Run a tor container that publishes hidden services that lets you ssh, ssb, and vpn to the underlying docker-machine host or VM parent machine.
Run:
make
The first time you run this, a new hidden service identity will be created.
For better anonymity, this project uses the longer SHA-3/ed25519/curve25519 .onion
addresses.
To ssh to the box in question, make sure your client has tor
running, then use torify
/torsocks
to run your ssh client connection:
torify ssh sshgxqz2vwpbgnmckeybbzsuuozpzdh6nwbcgtk7er6voqxklrhzh7qd.onion
which is effecively doing:
torsocks ssh sshgxqz2vwpbgnmckeybbzsuuozpzdh6nwbcgtk7er6voqxklrhzh7qd.onion
Alternatively, add some magic to your ~/.ssh/config
to allow you to ssh in with a simple netcat socks5 proxy:
Host *.onion
ProxyCommand /usr/bin/nc -xlocalhost:9050 -X5 %h %p
Then you can directly:
ssh sshgxqz2vwpbgnmckeybbzsuuozpzdh6nwbcgtk7er6voqxklrhzh7qd.onion
If you wish to create your own tor v3 vanity ssh address, you can use (cathugger/mkp224o)[https://github.com/cathugger/mkp224o] to generate your own vanity private/public keys, and replace the autogenerated ones under /var/lib/tor/ssh/
If you're doing this though, you're probably defeating the point of having the more secure v3 address to begin with.