Many applications, such as wget, apt-get, gpg, etc. do not speak socks, are unlikely to speak socks anytime soon, but support http.
Privoxy or polipo are of no help. They provides only one http port, with the one big drawback: all http connections will be presses through the same SocksPort (identity correlation [1]). torsocks is of no big help either. I think it has been designed, when identity correlation wasn't a big topic. By default torsocks uses /etc/torsocks.conf and also presses all applications started with usewithtor <app> into the same SocksPort (identity correlation again [1]). To me it also looks like torsocks is practically unmaintained, there is a critical bug open, IPv6 can leak real IP, no progress for a very long time. [2] In an ideal world, Tor wouldn't only offer multiple SocksPorts, but also multiple HttpPorts. That's for some reasons, either not going to happen anytime soon. [3] What other options left, to route, let's say, wget through port 9052, apt-get through SocksPort 9053, gpg through SocksPort 9054 and so on? [1] https://trac.torproject.org/projects/tor/ticket/6102 [2] https://code.google.com/p/torsocks/issues/detail?id=37 [3] https://trac.torproject.org/projects/tor/ticket/6060 ______________________________________________________ powered by Secure-Mail.biz - anonymous and secure e-mail accounts. _______________________________________________ tor-talk mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
