Date: Tue, 9 Jul 2002 16:15:14 +0100 (BST) From: Jan Grant <Jan.Grant@bristol.ac.uk> To: Michael Sharp <freebsd@ec.rr.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: SSH port forwarding Message-ID: <Pine.GSO.4.44.0207091604050.19306-100000@mail.ilrt.bris.ac.uk> In-Reply-To: <20020709022932.3022ac73.freebsd@ec.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 9 Jul 2002, Michael Sharp wrote: > Ok, I'm sure this thread is gonna elicit alot of humor, but I had to ask. I know how SSH port forwarding works normally using: > > ssh -C -L source-port:remote server:destination-port user@remote.server > > This makes remote server send a encrypted tunnel from destination-port to my local source-port... > > My questions is this, if I did: > > ssh -C -L 12345:freebsd.org:80 me@127.0.0.1 > > and logged in, would the traffic between and from http://127.0.0.1:12345 > be encrypted? Heh, yes, but that's not what you want. Between http://127.0.0.1:12345 and the browser running on your machine, yes. Between your machine and freebsd.org:80, no. There are reasonable pictures that demonstrate what's going on. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk "My army boots contain everything not in them." - Russell's pair o' Docs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.44.0207091604050.19306-100000>