If you would like to experiment or you are unable to install tor for some reason you can use the following address as a socks server:
tor-proxy.rrbone.net:9050
(You are able to chain proxies with tor, for instance using proxychains. Though I am not sure why one would want to do this because tor is extremity anonymous as it is. Also note to use this proxy server to access HTTP you MUST use a program like privoxy to tunnel HTTP traffic over socks. Also )
Tor is a very nice program that allows for an individual to be completely anonymous because of a group effort. Think of Zebra's on a network level. It is an anonymous onion router based mixer network. Its more than just accessing the open Internet anonymously. You can host "hidden daemons" where you can host any tcp server completely anonymously. People do some interesting things when they are anonymous and I suggest checking out some of these sites (Freenet is another example of this). But unlike Freenet tor is real time and a heck of a lot faster. There are IRCd's and SMTPd's hosted on tor, which you can't do on freenet. I am showing various security weaknesses in tor.
Tor allows for some interesting functionality, configuration and customization of tor is exceptional. The documentation is also very noteworthy, there is even a guide on how to set up your own tor network to suit YOUR needs. Thats really the magic of open source, you can customize the application to suit your specific needs, instead of being forced into a cramped cookie cutter, like a slave. Business is about excelling and doing better than the next guy, so why be constricted by insecure closed source software?
By default tor is secure. I'm not talking like Squid is secure by default or Windows 2003 is secure by default. One of the reasons why there are so many open proxies, people get "default secure" software, and to use it they compromise it. Tor is actually usable and secure by default. What a thought, maybe Microsoft could learn a thing or two from that. (Buying a $4000 OS that is useless by default? What a JOKE, that isn't security, that is running with your tail between your legs.)
What I am focusing on is the customization of Tor exit gates to the open Internet. Without them you would only be able to access tor hidden servers. Gateways are servers that are on 24/7, this is necessary because though your route to the gateway is quite dynamic because it is made up of users who are constantly joining and leaving the tor network. For Internet functionality to work properly you need a static ip address during the session. The tcp protocol is very robust and packets can be lost without loss of data or the connection. The more tor gates on the network, the faster you will be able to access the open net.
As a tor gate owner you have the amazing power to define what you want to exit your server. If you want you can only allow traffic to exit that is going to port 80 (http), or even a particular IP address or IP address range.
This is the default exit policy for tor:
reject 0.0.0.0/8
reject 169.254.0.0/16
reject 127.0.0.0/8
reject 192.168.0.0/16
reject 10.0.0.0/8
reject 172.16.0.0/12
accept *:20-22
accept *:53
accept *:79-81
accept *:110
accept *:143
accept *:443
accept *:706
accept *:873
accept *:993
accept *:995
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6881-6999
accept *:1024-65535
reject *:*
here is an example of someone modifying the exit policy:
http://archives.seul.org/or/talk/Mar-2005/msg00042.htmlI really like the reject *:*, so you have to specify what traffic you do want to allow, this is good security. If you notice port 25 is blocked, this restricts spammers from abusing tor. By default IRC is also not allowed, however if you have used tor you know you have no problems connecting to IRC. Some irc servers have k-lined some of the exit gateways due to abuse, but it is still possible to connect to these services. The ease at which you can connect to IRC demonstrates that these config files are being modified.
What is the potential impact of a modification? What would happen if someone allowed 127.0.0.1 aka loopback traffic?
To test this with your browser tell it to forward 127.0.0.1 though tor then try and access:
http://127.0.0.1 (you might have to refresh more than once.) At the time of this writing there is at least one apache server running giving you a directory listing.
What about services that are only available on the loopback because of serious security concerns? Keep in mind that windows SP2 turned the firewall on by default, and made it such that all windows services are only available to the local LAN or loop back. I will not divulge such services that are only loop back because they should ONLY be on loopback because I do not want tor gateways to be attacked.
What about access to the LAN?
There is a common trend of network security to have a "M&M Security"(this is done because its cheap and fairly effective) Where you have a hard outer shell and a soft inside. Someone could set up a tor network and potentiality expose there soft inner network to attack.
(Note it is not common however I have seen in some networks where they use 1.0-255.0-255.0-255 for internal use only, the 1.0.0.0 net block is reserved and my not be used for quite some time. This practice a dirty hack, but it gets the job done which is really all industry cares about anyway. Just remember that tor doesn't block 1.0.0.0 by default. )
I enjoy the tor network greatly and I would like it to be healthy. Apart of that is keeping it its gateways secure. Keep in mind that by default Tor gateways are secure, so don't be afraid of running a tor gateway. I urge people to modify there config files, I would like it if more ports where available by default, such as IRC. Just remember you MUST reject access to the local LAN and the loopback.
peace