Fantastic, I think this might be exactly what I wanted. Here is the entry from the manual page:
-via gateway Automatically create encrypted TCP tunnel to the gateway machine before connection, connect to the host through that tunnel (TightVNC-specific). By default, this option invokes SSH local port forwarding, assuming that SSH client binary can be accessed as /usr/bin/ssh. Note that when using the -via option, the host machine name should be specified as known to the gateway machine, e.g. "localhost" denotes the gateway, not the machine where vncviewer was launched. See the ENVIRONMENT section below for the information on configuring the -via option. It looks like the vncviewer will be secure. Kevin p.s. Hmmm... not working Here is my current working method: --Putty connects to hardware firewall, and firewall forwards all traffic on that port to my linux server. server is running ssh listener and manages connection. --PuTTY creates a tunnel: source port=59xx destination=localhost:59xx --vncviewer connects to localhost:1 (display 1). This network traffic goes through PuTTY, and comes out on the server as traffic from local host. -- After establishing the connection to the server, I run another copy of vncviewer to connect to the other PC with a local ip address (e.g. 192.168.0.5) I think that would need to forward the port 59xx in my firewall to direct it to my linux server. I think that doing this would be as secure as my SSH connection is, as it also requires log ins etc. I'll work on this some more. Kevin On 10/10/05, Mike Lieman <[EMAIL PROTECTED]> wrote: > On 10/10/05, Kevin Toppenberg <[EMAIL PROTECTED]> wrote: > > Thanks everyone for the input. I think I have decided it is too > > difficult to accomplish. I was hoping that I was missing something > > obvious. > > > > Thanks > > Kevin > > > > I need to draw a picture, let me show you how I do it... > > My Workstation. ( Linux, running vncviewer ) > aa.bb.cc.dd > | > | > The Internet > | > | > xx.yy.zz.aa > Remote Office Linux Firewall > 192.168.1.1 > | > | > | > Windows PC. (192.168.92.150 ) > > What I do is fire up a vncviewer, and use the -via command line > option to bounce it throught the remote office linux firewall. > Basically, it sets up the tunnel between my workstation and the remote > office linux firewall, and then the vnc connection to the windows pc, > without the dual overhead. > > $ vncviewer -via xx.yy.zz.aa 192.168.92.150 > > and viola. I'm on the 150 box. > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Hardhats-members mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/hardhats-members > ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
