joelol75 at verizon.net
Thu Feb 7 16:12:19 UTC 2008
A safer way is to tunnel your vnc traffic over SSH. Set up apache (or keep the Java applet local to the remote machine) and use the Java applet to tunnel to your ssh port (Which my default is NOT 22) You can even use my applet if you trust it to tunnel. It's at
This is actually triple protected (maybe overkill but...)
1. My SSH is on a non-standard port
2. My vnc port is NOT port forwarded so not visible to the internet
3. The whole session runs in a web browser, so no program is needed except for a browser and Java runtime (Yes this works on Windows guests.
So I goto https://stinker.serveftp.net and load the applet. Then go into FILE, New connection, and set my hostname (Use a free provider if you have dynamic dns (dyndns.org rocks) and enter the SSH port and select "password" authenticate. Then goto VNC settings and pick "Linux/UNIX host" leave hostname on localhost and set the display the vnc is running on (It automatically adds this to 5900)
I forgot where I got these .jar files but it works cross-site (Like bouncing my applet onto someone elses SSH server that has a VNC server behind firewalls whether its Linux Mac or Windows. Truly cool. I did this because there were so many exploits on VNC back in the day (And may still be... Did they ever get rid of the 6 character max pass length?)
Of course I wouldn't trust using my applet as I guess it could be set to harvest ssh usernames and passwords (Which I don't) but if you can find the Java pieces and set up apache and ssh you can host it on one machine and use it to get to all/any other machine without opening all the VNC server ports to the internet.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kubuntu-users