Re: Forwarding HTTP traffic through SSH using Windows

From: Simon Tatham (anakin_at_pobox.com)
Date: 07/25/03 

Date: 25 Jul 2003 15:40:16 +0100 (BST)

> >>>>> "DT" == Darren Tucker <dtucker@dodgy.net.au> writes:
> DT> Use "ssh -D 1080 desktop" to establish a DynamicForward then tell
> DT> your laptop to use a SOCKS server at 127.0.0.1 port 1080.

Richard E. Silverman <res@qoxp.net> wrote:
> I wouldn't recommend this until socks5 support arrives in OpenSSH.
[because SOCKS 5 allows the proxy to do the DNS lookup instead of
the client]

In case anyone might find it useful: a development Unix port of
Plink exists, works fine for me, and supports both SOCKS 4 and 5
dynamic port forwarding. So if OpenSSH won't do what you want, that
might. It'll even talk to OpenSSH's agent.

Incidentally, what happened to SOCKS 4A in that analysis? That
allows proxy-side DNS in what's basically SOCKS 4. Does OpenSSH not
support that either, or do web browsers typically not implement the
client side? (Plink supports that as well as SOCKS 4 and 5, natch.) 

-- 
Simon Tatham         "Thieves respect property; they only wish the property to
<anakin@pobox.com>    be their own, that they may more properly respect it."