Setting up Tor with Privoxy and Proxomitron

[laighleas]

Kye-U Wrote:Just installed Freecap to test it out with Proxomitron and Tor. I noticed that it only works with Socks 4, not Socks 5. When I set it to Socks 5, Proxomitron crashes.

Not sure what's happening there then. :-( I've got Freecap socksifying Proxomitron, and on SOCKS 5, and it's dead stable. Works like a dream - you hardly notice Freecap is there - it's set to run Proxomitron the moment it runs.

For reference, my OS is XP sp2 with .NET. I've patched tcpip.sys to get round the limits Microsoft have imposed upon it in the name of 'security' (EventID 4226), but that shouldn't have any effect that I can see. Or does it?

Kye-U Wrote:Perhaps I'll start on another guide to using Tor with Freecap and Proxomitron

It's fairly simple. Just add a new application, and point it at 9050. In fact you can set that as your default proxy. The only wrinkle I'd add - with SOCKS 5 - is set it to resolve names remotely, thus forcing the Tor system to look up hostnames remotely, and thus avoid DNS leaks. You'll still get an occasional warning from the program that you're using SOCKS 5 and that you may have a DNS leak because Tor is receiving an IP. This, however, is spurious, and is apparently based on the following assumption: if Tor receives an IP, this has been resolved elsewhere - presumably your system has resolved the name locally, thus advertising to all and sundry where your traffic is now bound.

It's a bit of a hiccup, and is due to the program erring on the side of caution. There's a whole load of guff about it here:

http://wiki.noreply.org/noreply/TheOnion...7f717a9be1

This issue is on their To Do list.

Anyway, I sat there for at least an hour or two trying to make the Freecap/Proxomitron combination misbehave, and checking for leaks with Active Ports. Steady as a rock, and nothing connected except through Tor, so I can guarantee the network was doing any resolving necessary. So as I said, a spurious warning.

Kevin