Stream Isolation: Easy

From Whonix
Jump to navigation Jump to search
New illustrative Whonix stream isolation image with 4 Tor relays. (Instead of 3 in the past.) See also vanguards.

Whonix Tor Stream Isolation Short Introduction

Applications such as Tor Browser, ssh, gpg, wget, curl, git, and apt are configured for stream isolation by default; the full list can be found here. The advantage of this configuration is that these applications will take different paths through the Tor network and will therefore be more anonymous, since it protects against identity correlation through Tor circuit sharing. [1]

This arrangement comes with a small usability impact in corner cases:

Further information:

Footnotes[edit]

  1. If stream isolation is not enforced, different activities conducted in separate applications may pass through the same Tor circuit and exit relay, correlating these activities to the same pseudonym.
  2. It might be required to disable stream isolation for applications that require local connections. For example, this is the case for opening a local ssh listener:
      • If the following command is run: ssh 10.152.152.11, uwt will actually execute torsocks /usr/bin/ssh.anondist-orig 10.152.152.11. In this case, traffic would flow though torsocks via a Tor SocksPort. This will fail for local connections and lead to the following error message:
        • libtorsocks(12021): connect: Connection is to a local address (10.152.152.11), may be a TCP DNS request to a local DNS server so have to reject to be safe. Please report a bug to https://gitweb.torproject.org/torsocks.git/archive.org if this is preventing a program from working properly with torsocks

      • This is possibly no longer required thanks to the Whonix default /etc/tor/torsocks.confarchive.org configuration file which sets AllowOutboundLocalhost 1.
    # Set Torsocks to allow outbound connections to the loopback interface.
    # If set to 1, connect() will be allowed to be used to the loopback interface
    # bypassing Tor. If set to 2, in addition to TCP connect(), UDP operations to
    # the loopback interface will also be allowed, bypassing Tor. This option
    # should not be used by most users. (Default: 0)
    AllowOutboundLocalhost 1
    

We believe security software like Whonix needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!