So, there comes a time in a man’s life when people at work on the inside network need to access things on the internet. This is called “proxying”. Yes, yes, I know; very fascinating. These secure machines on the inside network don’t have access to the internet by design (See RFC 1918). It’s the most basic layer of obfuscation (a 25 cent word we use a lot in the security world) and protection from bad internet traffic, not including firewalls and all that other exciting stuff.
Ok so we want to let our secure hosts on the inside proxy SSH to the internet via our SOCKS server.
- A Unix/Linux machine with the latest version of netcat installed (assumed to be found at /usr/bin/nc). All modern operating systems have this. Stop whining.
- A SOCKS proxy listening on TCP port 1080.
- A remote internet server listening for SSH connections on TCP port 22.
- You know what ~ means. (Hint: It’s shorthand for your home directory.)
Create an entry in ~/.ssh/config. If this file doesn’t exist, create it. If it does, add this shit to the bottom:
Host proxythatshit ProxyCommand /usr/bin/nc -X 5 -x proxy.whatever.com:1080 internet.com 22Write, quit, and then test that shit! I am hoping that you gathered “proxythatshit” is the nickname we’re assigning this proxied connection to internet.com. By putting this stuff in the config file, it makes it easy to reuse.
% ssh proxythatshit jathan@proxythatshit's password: [email@example.com]~%Did you see that? It worked!! OMGZ!!JLk
A little breakdown:
ProxyCommand /usr/bin/nc -X 5 -x proxy.whatever.com:1080 internet.com 22
- ProxyCommand: An OpenSSH directive that tells SSH how to proxy the connection
- /usr/bin/nc: The path to the netcat binary and the ProxyCommand in question here. Proxying is one of the many things netcat does.
- -X 5: Tells netcat to use SOCKS version 5
- -x proxy.whatever.com:1080: Tells netcat to proxy the connection using proxy.whatever.com on port 1080
- internet.com 22: The name and port of the destination we’re trying to get to by way of the proxy
You may be asking yourself, “Why not just use an HTTP proxy?” Because HTTP proxies tend to be very picky about allowing you to proxy non-HTTP connections to destination ports other than the one you connected to. In other words, if the proxy is listening on port 8080, good luck proxying a connection that isn’t HTTP (such as this SSH proxy thing) on anything other than port 80, 443, or 8080 it probably won’t work. If you’re using mod_proxy, it absolutely will not work. Don’t ask me why. It just doesn’t. Squid might work, but it is a pain in the ass to setup.
There you have it. Don’t blame me if you get fired because you were looking at a picture of a monkey fucking a coconut for the 52 seconds it took to read this.