[plug] SSH Tunnel

[Bennett, Phillip]

Mike,
 
Server2 doesn't need to support SSH directly.
 
When you set up the link in putty from work (I'm guessing this is from
work) to server1, you put a tunnel in the tunnel section as I described.
This makes it look as such:
 
 
 
work----(SSH Encrypted)----> server1 ----(unencrypted)----> server2
 
Then when you use your local port 9999 the data will go straight through
to server 2.  The data will be encrypted bewtwwen you and server1, but
not between server1 and server2.  It will also look to server2 as if the
data/connection is coming from server1.

An example is when I connect to home from work.  I set up a tunnel so I
can use my proxy server at home.  In the squid logs, it says the
connections are coming from an internal address.
 
Hope this doesn't confuse you too much, but it WILL work.  Attached is a
screenshot of how the tunnel should look.
 
hth,
Phil.
 
PS: I see there is now another message on the list explaining this also.
I'll send this anyway. :)
 
 

________________________________

From: plug-bounces at plug.org.au [mailto:plug-bounces at plug.org.au] On
Behalf Of Michael L. Benjamin
Sent: Thursday, 6 April 2006 10:43
To: plug at plug.org.au
Subject: RE: [plug] SSH Tunnel


 
Hi Phil,
 
Server2 (pop3) doesn't offer SSH, therefore the last hop on the link has
to be un-encrypted.
 
I figure I could do something with netcat... I'll keep playing with
it...
 
Mike.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tunnel ex1.png
Type: image/png
Size: 8957 bytes
Desc: tunnel ex1.png
URL: <http://lists.plug.org.au/pipermail/plug/attachments/20060406/72e70053/attachment.png>