Custom SSH ports with sshuttle


Icon from the Tango Desktop project Icon from the Tango Desktop project

I’d tried 0.1 back in the day, but @OliYoung reminded me this morning of sshuttle, the poor man’s VPN that’s just too much fun!

On Soviet Internets, sshuttle proxies you

For most all of my SSH connections, I use custom ports. Security through obscurity is a dangerous misnomer if only used by itself, but it helps to lower the chances of a roaming bot scanning on port 22 from finding it.

With a regular SSH connection you define a port with -p, though fancy alliteration is not necessarily required:

% ssh -p 60000 username@SuperSexySSHServer

Sshuttle doesn't have a -p option, so you merely append the port old school style:

# sshuttle -r username@SuperSexySSHServer:60000 -vv

This then gets converted into a -p option when sshuttle initiates the required SSH connection.

Starting sshuttle proxy.
Binding: 12300
Listening on (‘′, 12300).
firewall manager ready.
c : connecting to server...
c : executing: [‘ssh’, ‘-p’, ‘60000’, ‘username@SuperSexySSHServer’, ‘–‘, ”python’ -c ‘import sys; skip_imports=1; verbosity=2; exec compile(, “”, “exec”)”]

I would know, because I’m using it to write this blog post! Very cool :)

Author bio and support


Ruben Schade is a technical writer and IaaS engineer in Sydney, Australia who refers to himself in the third person in bios. Wait, not BIOS… my brain should be EFI by now.

The site is powered by Hugo, FreeBSD, and OpenZFS on OrionVM, everyone’s favourite cloud infrastructure provider.

You can leave me a comment by contacting me, and I might publish your thoughts. Please read the FAQs first though.

If you found this post helpful or entertaining, you can shout me a coffee or buy some silly merch. Thanks!