As such, Tor wrappers are not a secure isolation mechanism. Tor wrappers cannot reliably prevent an application from establishing connections outside of the Tor network they merely ensure that non-malicious code using networking APIs in straightforward ways have their direct connection attempts routed via Tor. This allows non-Tor-aware, non-SOCKS-aware applications to have their traffic routed over Tor. Tor wrappers such as torsocks and tsocks can be used to intercept network API calls in applications to direct network activity over a Tor socks port. Tor wrappers: torsocks, torsocks-faster and tsocks It is highly advisable to route HTTP traffic via Privoxy rather than via SOCKS directly. Privoxy listens on port 8118 and is configured to route to the fast SOCKS port.

This is a 'fast' SOCKS port suitable for browser use a new circuit is established every ten minutes.īy default, the Privoxy HTTP proxy is enabled if you enable Tor client functionality ( ).

This is a safe default which complicates identity correlation attacks, although isn't sufficient to completely thwart them.īy also enabling, an additional SOCKS service on port 9063 can be enabled. 9050 is a 'slow' SOCKS port which can be used for email, git and pretty much any other protocol but HTTP(S) since a new circuit will be created for each destination IP. settings = īy default Tor in NixOS provides one SOCKS proxy on port 9050.

Tor switch wiki