HTTP proxy through SOCKS
One of the easiest ways, I find, to use a proxy is to use Putty to create a local SOCKS proxy and configure the browser or application(*) to use this SOCKS proxy. Unfortunately, many applications don’t support SOCKS but do support HTTP proxies. (wget is one of those applications that don’t support SOCKS but unlike many others wget can still use an SSH tunnel.) But there’s a trick we can use from the Tor-Project: use Privoxy.
Privoxy is a small HTTP proxy that can optionally route all traffic to another HTTP or, and here’s the thing, SOCKS proxy. After the installation of Privoxy there’s just one line to add to its main configuration file, config.txt:
This will tell Privoxy to route all traffic through the SOCKS server at localhost port 9050. The port 9050 is the port you configured in Putty’s dynamic routing tab or after the -D command line option in Plink. By default, Privoxy listens on localhost:8118 so reconfigure your program to use that as a HTTP proxy and you’re set. Note that you will have to restart Privoxy after making a change to its configuration file.
- or the old FileZilla 2.x; the new one does not support SOCKS and the old one is nowhere to be found