TightVNC remote desktop

[b0redom]

Just doing some more investigating

Sooooo if I use PuTTY for the SSH connections, configure it to use port 22 on both systems and then launch tightVNC over it - does that work?

In putty there is an option for port forwarding

Configuration->Connection->ssh->tunnels

add a forwarded port:

local 5900
remote myipaddress:5900

local 5800
remote myipaddress:5800

...then connect to your machine as usual using ssh and point tightvnc at localhost instead of your machine's IP address. SSH tunnelling will take care of the rest for you....

[El_Diablo]

Crossloop is not bad.

[Troll]

found crossloop - Tight VNC & ssh tunneling all in an easy to use package - only issue is it needs admin rights to run

[Troll]

Just doing some more investigating

Although TightVNC encrypts VNC passwords sent over the net, the rest of the traffic is sent as is, unencrypted (for password encryption, VNC uses a DES-encrypted challenge-response scheme, where the password is limited by 8 characters, and the effective DES key length is 56 bits). So using TightVNC over the Internet can be a security risk. To solve this problem, we plan to work on built-in encryption in future versions of TightVNC.

In the mean time, if you need real security, we recommend installing OpenSSH, and using SSH tunneling for all TightVNC connections from untrusted networks.

Sooooo if I use PuTTY for the SSH connections, configure it to use port 22 on both systems and then launch tightVNC over it - does that work?

[r0bly0ns]

I've recently started using it on my internl network as it's much faster then going out to the net for LogMeIn.


I am tempted to use it remotely over the net, but am also concerened about security.

[Troll]

Has anyone used this? it seems to almost too easy to setup & use - much more preferable to XP native RC!

Are there any known security issues
I've setup challenge authentication and timeout on connections, it seems to be all there is !