One way to make encrypted VNC connections that doesn't
require an open TCP port is to use EchoVNC alongside your VNC
Server. EchoVNC lets you make a "firewall friendly" connection
using a relay server that you own and control (e.g., running on
your public Linux server). Data content is secured with 128-bit
AES via the OpenSSL toolkit, and it works with any flavor of VNC.
More info here:

For remote users who are not allowed to install their own
programs, try using EchoWinVNC. It's a zero-install "single click"
version of VNC that you can easily customize to connect to your
relay server, and even display your own splash-screen.


On May 5, 2006, at 1:00 PM, Russell Howe wrote:

> On Fri, May 05, 2006 at 04:52:44PM +0200, Morten W. Petersen wrote:
>> Hi,
>> we have some remote users that need help setting up various tools on
>> their computers, and we would like to be able to do this for them via
>> VPN, having them for example downloading an application and
>> starting it
>> so we can access their computer.

> If you don't mind the unencrypted-ness (which you probably should),
> why
> not just get them to install VNC and run a viewer on your end in
> listen
> mode. That way they can just connect to your listening viewer, giving
> you control.
> No need to even install VNC such that it has a listening socket.

VPN mailing list