What I know is that installing the Debian torsocks package just works, without any custom configuration. Doing "torsocks wget ipchicken.com" and looking at the resulting index.html, I see Tor exits. Even building, I don't believe that you need to configure the SocksPort. It's setup by default to use Tor.

Strange. Long time ago, Tor client in the Browser Bundle had changed its listening port to 9150, standalone Tor is 9050. For now I removed /etc/tor, so torsocks would use it's default configure settings, but the problem is still remain and connecting to the Internet without going through Tor network.

What I know is that installing the Debian torsocks package just works, without any custom configuration. Doing "torsocks wget ipchicken.com" and looking at the resulting index.html, I see Tor exits. Even building, I don't believe that you need to configure the SocksPort. It's setup by default to use Tor.

Click to expand...

Do you install the standalone Tor or you install from repository? The document saying the torsocks is work with the daemon, what torsocks work with?

If you're using Tor browser, just add the line "SocksPort 9050" to that torrc-defaults file that I pointed to. Then the tor instance that Tor browser runs will provide both SocksPort 9150 for the browser, and SocksPort 9050 for torsocks. But you'll need to have Tor browser running in order to use torsocks.

Also, there's a lot more to a safe Tor setup than torsocks. DNS leaks are a huge risk.

Why not just use the Whonix gateway and workstation VMs in VirtualBox?