21

Browsing different websites At the moment, it is not advisable to browse two different websites at the same time when you don't want your activity to be linked. The Tor client can't tell which tab/window you are using for each request so might send requests for both sites over the same circuit. The exit node operator could then spot the correspondence. ...


4

Written in September 2013, this answer might be out of date after some time. Full disclosure: I am a maintainer of Whonix wrote most of this page, so I may be biased. (By the way, that page is under a Free as in speech license, so if you legally copy it to wikipedia (or similar) it can be made truly objective.) If you are most concerned about local ...


3

If you don't want two things to be linked, don't do them on the same machine. The simplest approach would be to use multiple instances of Whonix. Whonix is a pair of VirtualBox Debian VMs. One runs Tor, and the other is workspace with Tor-optimized Firefox etc.


1

An RSS feed is no different than other web resorces: to browse it anonymously via Tor, connect to each site individually, one new circuit per site. As it stands today, RSS feed aggregators just aggregate several feeds from a user-predefined list, retrieving it in the background and presenting it in an UI. Taking e.g. Tiny Tiny RSS, an OSS self-hosted PHP ...


1

"it'll cause a major performance hit" Yes, it'll build far more circuits than are necesary and won't fix isolation problems. "make my traffic more identifiable" You'll certainly have non-standard traffic patterns. An adversary could also try to intentionally cause denial-of-service conditions by, for example making you attempt to build a circuit to every ...


1

Not sure about adding more rules but from what I understand having a drop all incoming and outgoing policy is a good thing to start from. Afterward , building your rule-set to punch holes in the wall. The addition of the lo rules is needed in a set up like that so it's good that you added them there. So, since you only have two major rules, EVERYTHING is ...


1

There is no way to use the transparent proxying features with modern OS X. Apple removed ipfw (which is what natdport would use), and doesn't provide headers for pf so Tor can't reliably use it and disables the feature while building.


Only top voted, non community-wiki answers of a minimum length are eligible