Also, users on a MS-windows PC might not want to run Tor locally as to not run into any shenanigan by the vendor or attacker. For some others, the extra workload might seem OK, for example if they already have fully deployed and available a remote host to ssh into. So why do it? Some will reject the notion of the tor-ssh-tunnel and just stick with the TorBrowserBundle having almost the same benefits. Privoxy is bound to break a number of websites. Motivation: This method clearly is tedious to set up (more so than an ssh tunnel), difficult to maintain, introduces many possible points of failure, introduces a shitload of new passwords in danger of being forgotten, adds complexity, is hard to understand and operate. Here we use both a http-proxy as well as a remote tornet-proxy for anon web-surfing secured by ssh Using ssh port forwarding, we can connect to a Tor proxy on a remote machine - rather than running tor locally, say inside of TorBrowserBundle ('TBB'). 3.2 actually using the finished ssh tunnel.3.1 Tell SSH to connect to a remote port.3 websurfing on browserhost using Tor on irchost.1.1.5 ssh from browserhost into irchost with an authorized key.1.1.4 disable password login on irchost (optional).

1.1.2 on browserhost, transfer the public key to irchost.1.1.1 on browserhost, generate an SSH public/private key pair.

Setup tor proxy linux