[FoRK] Poisoned DNS on the increase

[Bob Ippolito]

On Feb 18, 2008 3:08 PM, Andy Armstrong <andy at hexten.net> wrote:
> On 18 Feb 2008, at 22:57, Lucas Gonze wrote:
>
> > On Feb 18, 2008 2:02 PM, Andy Armstrong <andy at hexten.net> wrote:
> >> The browser will look up the name of the proxy using local DNS but it
> >> won't attempt to resolve the target hostname I don't think. I could
> >> plausibly be talking out of my arse though :)
> >>
> >> I assume it must work this way because proxies are usable in
> >> environments where there is no DNS.
> >
> > This would be pretty central, I think.  :)
> >
> >>> I have to admit that I haven't yet figured out how to tunnel my HTTP
> >>> traffic over SSH when I'm using a public access point. :*(
> >>
> >>
> >> You want an SSH invocation that does it?
> >
> > Got one handy?  I'm in for sure.
>
>
> I had to check - otherwise I'd have just posted it :)
>
> $ ssh -L 8080:localhost:8080 myproxy.example.com
>
> The first 8080 is the local port that you'll connect to, the second
> 8080 is the port the proxy is listening on on the remote host. For
> that to work the proxy has to be bound to 127.0.0.1 on at the remote
> end. If the proxy is instead listening only on myproxy.example.com use
>
> $ ssh -L 8080:myproxy.example.com:8080 myproxy.example.com
>

You can skip the need for a proxy server altogether, SSH has a
built-in SOCKS4/SOCKS5 proxy.

$ ssh -D 8080 myshell.com

Then just configure your browser and/or OS to use 127.0.0.1:8080 as
the SOCKS proxy.

-bob