The traffic is indeed encrypted between you and the Tor entry server. I also wanted to see if anything showed up in the web proxy logs (Irun a transparent proxy). No suprise there, nothing showed up, since of course all the traffic is going to port 9001 and is therefore not redirected to the proxy.

I did catch one conversation that wasn’t encrypted, though. I don’t know why. Perhaps it defaults to no encryption if on of the servers on the circuit doesn’t support it? Couldn’t find an option to enforce the use of encryption, though, nor could I find any way to choose which encryption to use.

One thing it’s missing is the ability to exlude certain entry servers from the selection algorithm. If the NSA happens to be running a Tor server, and I feel the need to go through Tor to hide my tracks, I really *don’t* want my traffic going to the NSA (or CSIS).

I also would have liked to have seen some sort of speed measurement, whereby I would be able to test several curcuits out before selecting one. But the biggest problem I had was in making the initial conection to the entry server. Three times out of four starting the TorPark browser I was denied the connection, or it timed out.

The really nice parts are the ability to force an IP change, or rather, to switch circuits and use a different exit server, anytime you wish, and you are also able to force IP changes at an interval of between 17 and 1422 minutes, so your IP changes automagically. That option might create problems with some authentication schemes, though, so by default, your exit server does not change regularly. You can even randomize your browser name and change the user-agent string easily through the extensions menu.

All in all, a very well written and convenient application, although it can definitely be expanded on and improved.