As I’ve mentioned a couple of times recently1 2, I have set a handful of different things on my local machines to make remote development a bit easier. This time around, I have two more to add to that list:
- Setting up a local SOCKS proxy with SSH
- Setting up a local TOR proxy for testing / more anonymous browsing
- Configuring your browser to use these proxies for some/all traffic
In both cases, I have these running on an always-on server that I use for various projects just like this. It could just as easily be set up to run on a Raspberry Pi or on your local machine.
Setting up a SOCKS proxy
To set up an SSH
DynamicProxy, the easiest way I’ve found is to add it to your SSH config:
In this case,
bastion.example.com is running SSH on port 6622, which we are connection to. We’re then setting up the local port
7769 to accept incoming connections on the
SOCKS5 protocol. Then you open the tunnel with:
$ ssh workproxy
The SSH connection has to stay open in order to use the proxy, so it’s best if you run it in a tmux or screen session (I prefer tmux personally). You could also use something like autossh to automatically restart it, but thus far, I’ve not particularly found it necessary.
Adding an HTTP/HTTPS proxy
In most cases, that’s all you need.
When I first set this up, I also wanted to be able to use an HTTP/HTTPS proxy, which meant that I wanted to use something like Polipo3. Apparently though, in the face of pervasive HTTPS traffic, Polipo has is no longer being maintained. I actually learned this as I was writing the post. TIL.
In any case, the set up I had for Polipo was:
$ polipo \
socksProxyType tells it that we’re going to use an SSH
DynamicTunnel proxy and
socksParentProxy tells Polipo where it is.
proxyPort is where the new Polipo proxy will be listening, while
proxyAddress is necessary so that hosts on other machines can here it as well (this could be far more restrictive, but I’m using my router to prevent external traffic to that port, so I don’t have to limit this).
allowedClients lets other hosts on the same network connect and the last two options are just for logging.
That’s really it. Set the
HTTPS_PROXY environment variables (possibly with Dynamic Automatic Proxies 😄) and many things will automatically use it. That’s actually why I still have Polipo still running despite the deprecation warning. It does what I need it to do, in particularly when using the AWS CLI and/or the Python requests library, which both accept HTTP/HTTPS proxies, but not SOCKS5.
If/when I can figure out how to configure those to use SOCKS54, I can stop running Polipo, but until then, this works.
Setting up a TOR proxy
Next up, we can use a TOR proxy. If you absolutely need a guarantee that none of your traffic is going to leak your identity (for any number of reasons), this is probably not the way you want to go. If that’s the case, you should at least be running the Tor Browser. Or even better yet, run Tails in a virtual machine on a burner laptop.
However, if you’re just looking for a basic / better than nothing level of anonymity–which I generally use for testing things that should be restricted to internal networks or behave differently on externals ones.
docker run -it -p 8118:8118 -p 9050:9050 -d dperson/torproxy
That’s it. It exposes a SOCKS5 proxy that routes to the TOR network on port 9050. That’s it. If you wanted, you could put Polipo in front of it same as above for an HTTP/HTTPS proxy, but I haven’t needed to.
Configuring your browser
In order to use the SSH proxy, we set the host and port and then set the protocol to SOCKS5:
Likewise for TOR:
One thing that I particularly enjoy about Proxy SwitchOmega is the ability to dynamically choose proxies based on hostname. For example, if I wanted to visit a .onion domain (only available via Tor), I could set up a rule like this: