Call for Privacy : Episode2
posted on 06 Mar 2007 22:28 by exploitcatz
This 2nd episode of "Call for Privacy" series should never be published if something terrible actually happened. But since there was nothing in particular, my tunnel will be running every day as usual :D
Tor sure is the the answer when it comes to the anonymous stuff. You all the readers should be familiar with the onion for sure :D
But now I will point to how to use tor at your workplace (Yes, that's the goal of this series). Since you can't just use tor at your workstation at your workplace because of following 2 reasons:
1. You may not be allowed to use unusaul ports that tor uses.
2. If you are able to use tor, you still can't - -". Because using tor doesn't mean encryption, your IT department still able to see all the traffic travelling out of your box.
Thus we have to consult our old tunnel, plus a little config to make use of tor running at home. It's still that easy:
* Note that we need tor to be running properly at your SSH server at home (The previous Episode doesn't require tor).
PuTTY
Very easy as always. At tunnel section (you know where it been), just enter '7070' in 'Source port' and '9050' in 'Destination', then connect to your SSH servre as usaul.
OpenSSH
Very bloody easy as always for OpenSSH. Just like before, a single command is needed:
** 7070 is a port you'd like to open locally on your box at workplace.
** 9050 is a port that you configure tor to listen locally (or publicly, it doesn't matter) on your SSH server at home (9050 is a default value).
Reference:
TOR howto: Using TOR through a ssh-tunnel
Tor sure is the the answer when it comes to the anonymous stuff. You all the readers should be familiar with the onion for sure :D
But now I will point to how to use tor at your workplace (Yes, that's the goal of this series). Since you can't just use tor at your workstation at your workplace because of following 2 reasons:
1. You may not be allowed to use unusaul ports that tor uses.
2. If you are able to use tor, you still can't - -". Because using tor doesn't mean encryption, your IT department still able to see all the traffic travelling out of your box.
Thus we have to consult our old tunnel, plus a little config to make use of tor running at home. It's still that easy:
* Note that we need tor to be running properly at your SSH server at home (The previous Episode doesn't require tor).
PuTTY
Very easy as always. At tunnel section (you know where it been), just enter '7070' in 'Source port' and '9050' in 'Destination', then connect to your SSH servre as usaul.
OpenSSH
Very bloody easy as always for OpenSSH. Just like before, a single command is needed:
That's all! As of now whenever you configures your client to use socks at 127.0.0.1:7070, it means you are using tor at your home !!
$ssh -L 7070:127.0.0.1:9050 username@sshserver
** 7070 is a port you'd like to open locally on your box at workplace.
** 9050 is a port that you configure tor to listen locally (or publicly, it doesn't matter) on your SSH server at home (9050 is a default value).
Reference:
TOR howto: Using TOR through a ssh-tunnel