600x is the X server port. It has known vunerabilities (XFree86, for example
had a simple one-packet DoS attack on its port; this is probably still
present in Xvnc, since it's based on XFree86).
The X security is not very strong, either; what's more, people often turn it
off (the command 'xhost +
On Thu, 17 May 2001, Michael Procter wrote:
> Mike, I did against a couple of my Linux boxes and had no problems,
> whether the viewer was open or not.
Thanks. I tried a different Sun and it did *not* crash. That Sun is
running Solaris 2.5.1 while the others were running Solaris 2.6. All
mach
Mike Miller wrote:
> On Wed, 16 May 2001, Scott C. Best wrote:
>
> > > If I run nmap on another machine as follows:
> > >
> > > nmap -p 6001 host.machine
> >
> > Instead of running nmap on all those ports (the -p ,
> > without the number, scans all the low numbered ports <1024, plus any
> >
On Thu, 17 May 2001, Scott C. Best wrote:
> Hello! I'm sorry that my suggestions don't sound appealing to
> you. It sounds like you found a potential weakness in a VNC system,
> but are dis-inclined to gather more data about the particulars. My
> experience with open source projects over th
Mike:
Hello! I'm sorry that my suggestions don't sound
appealing to you. It sounds like you found a potential
weakness in a VNC system, but are dis-inclined to gather
more data about the particulars. My experience with open
source projects over the years is that the person who calls
in the
On Wed, 16 May 2001, Scott C. Best wrote:
> > If I run nmap on another machine as follows:
> >
> > nmap -p 6001 host.machine
>
> Instead of running nmap on all those ports (the -p ,
> without the number, scans all the low numbered ports <1024, plus any
> that come with the nmap config files
Mike:
Hello! Some thoughts on what you're seeing:
> If I run nmap on another machine as follows:
>
> nmap -p 6001 host.machine
Instead of running nmap on all those ports (the
-p , without the number, scans all the low numbered
ports <1024, plus any that come with the nmap config
