I've been playing recently with the web-delivered java vnc client available on most VNC installs (using Tight myself at the moment) at this url http://yourhosthere:5800 and was curious if anyone developing on VNC had looked at encryption from that standpoint, i.e. with maybe ssl encryption. I mean, you've already got a minimal "web server" there to load the java client, is it really that much of a step to do an SSL-tunnel?
> -----Original Message----- > From: Paul Hosking [mailto:[EMAIL PROTECTED]] > > (snip) > But... the rest of VNC traffic is unencrypted. So your > session is prone > to snooping (although the traffic has to be uncompressed > first). You'll > note several methods to protect this traffic in the > above-mentioned FAQ > link. My often-used favorite is a SSH tunnel. SSH will > provide better > authentication, encryption of the traffic, and even some > compression if > you need. > > Finally, if you need a bit more efficient VNC, TightVNC is an > excellent > off-shoot of the origional VNC project: > > http://www.tightvnc.org/ > > I tend to prefer TightVNC as I am never quite sure what kind > of network > link my laptop will be hanging off of when I need it (which only > re-enforces the use of a SSH gateway / tunnel).
