there's no point in vino setting up an ssh tunnel. Your vnc client perhaps should set it up, but not vino (you wan't the tunnel from your "client" to your "server" so vino can't do it.
The problem is, that vino a) doesn't give the option to bind to localhost only b) deals in unencrypted sessions/passwords hence if one doesn't want to allow unencrypted sessions/passwords on services exposed to the world, one can't use vino. The only thing I'd correct about my patch in that case (well design wise, its fairly ugly patch overall) is to say that "localhost" isn't default selected. -- vino listen on all addresses https://launchpad.net/bugs/54312 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
