So yesterday I made a very detailed post about using SSH to get around networks and use torrents anywhere you want. I thought about it more last night, and realized I should elaborate a bit more on WHY it works. Basically, when you torrent stuff, you connect to a tracker, just a regular website, and say 'Hey, I wanna download THIS file, who has it?' and the tracker says 'Here is the list of everyone who does, and everyone who has some of it' (aka seed/peer counts). Then your torrent client does some stuff to pick out the best seeds for you, and connects to them. Then you start to download the file.
When IT people look at their traffic, they will suddenly see some traffic popping up on some random port, 61324 lets say. They can then look at the stream of data, and they can see very easily that you're downloading music or movies or games.
What we do to fix this is run all of our traffic through SSH. You might be wondering why they can look at the torrent traffic, but not the SSH traffic... good question. The answer is that all SSH communication is encrypted. Yes the IT people could unencrypt it with a lot of work, but they wont. I will personally guarantee this. SSH traffic is usually expected to be used for remote systems or any other application where you want data to be encrypted.
You may have realized this by now, but SSH is just a tunnel that the IT people can't look into. It has nothing special to do with torrents. So you can apply the same settings explained in my last post to ANY application that supports a Socks4 or Socks5 proxy.
If you have any more specific questions about SSH, Google first, then ask me in the comments if Google fails. haha.
No comments:
Post a Comment