{{Header}}
{{#seo:
|title=Stream Isolation
|description=Prevent Identity Correlation through Circuit Sharing by using Tor Stream Isolation.
}}
<!--
[[File:WhonixStreamIsolation.jpg|thumb|New illustrative {{project_name_long}} stream isolation image with 4 Tor relays. (Instead of 3 in the past.) See also [[vanguards]].]]
-->
<div class="mininav">
* [[Stream_Isolation/Easy|short stream isolation summary]]
* [[Stream Isolation|all information below]]
</div>
{{intro|
Prevent Identity Correlation through Circuit Sharing by using Tor Stream Isolation.
}}
<!--
[[File:Stream-isolation-promo.jpg|thumb]]
-->
[[File:Streamisolationme.jpg|thumb|Old illustrative {{project_name_short}} stream isolation image.]]

__TOC__
== Introduction ==
=== Essentials ===
If the internet is used normally, without Tor, a proxy or VPN, there is not really a widespread term for this. Could be coined "connecting over clearnet".

When using Tor without {{project_name_short}} such as when using the Tor Browser Bundle on a host operating system such as Windows or Debian, only the Tor Browser Bundle connect over Tor. All other applications are still using clearnet.

In case of {{project_name_short}}: {{TorifiedGateway}}

=== Transparent Proxy ===
This chapter explains what a Transparent Proxy is. It is required to know in order to understand the following chapters.

* Transparent proxying means, simplified and [[unspecific|unspecific to {{project_name_short}}]]: <blockquote>An application can connect without additional configuration required.</blockquote>
* Use Firefox on host operating system without Tor or any proxy/VPN without {{project_name_short}} involved: Not sure that should be called that "transparent proxying". Should probably not call it that way to avoid confusion. In that case probably the home router is doing "transparent proxying". A proxy that is transparent. It does stuff for the user/program without the user necessarily having to know anything about it.
* Using Tor Browser on the host without {{project_name_short}} involved: This is an example for "no transparent proxying available". <ref>
Tails used to have transparent proxying (could use any application without configuration). Nowadays Tails has no transparent proxying. (Most) Custom installed applications (example: Mozilla Firefox) won't connect without manual configuration in Tails.
</ref>
* There are also other types of transparent proxies such as content filtering, virus scanning, and what not.
* More complex specific to {{project_name_short}}: <blockquote>An application can use TCP/DNS [UDP blocked] over Tor (user -> Tor -> destination) without additional configuration required.</blockquote>

{{project_name_short}} has feature <code>transparent proxying</code> enabled by default. <code>transparent proxying</code> is a feature that most users want. Not enabling <code>transparent proxying</code> by default would be confusing for most users.

In other words, {{project_name_gateway_short}} by default can be used as a Tor Transparent Proxy. Connections from {{project_name_workstation_long}} to {{project_name_gateway_short}} are transparently proxied through Tor.

For example if using [[Telegram]] in {{project_name_short}}: Uses transparent proxying because it is not pre-configured by default to use Tor proxy settings.

=== Identity Correlation through Tor Circuit Sharing ===
If the user installs custom applications and omits to explicitly take precaution against {{Code2|identity correlation through Tor circuit sharing}}, the user is risking that different activities, let's say web (Chromium or similar) or IRC (mIRC or similar) go through the same Tor circuit and Tor exit relay. Even though the user would still be anonymous, i.e. the Tor exit relay would still not know the user's real IP/location, the Tor exit relay and their internet service provider (ISP) can easily correlate those activities by different applications to the same pseudonym.

The following graphic illustrates the difference of using Tor <code>SocksPort</code>'s compared to using Tor's <code>TransPort</code>. Using a dedicated Tor <code>SocksPort</code>'s per application results in taking different routes through the Tor network per application. Not necessarily all Tor relays (first, second, third) get replaced by Tor. Sometimes just the first, sometimes just the second, sometimes just the third, and sometimes multiple Tor relays in the Tor circuit change.

[[Image:stream_isolation.1.0.jpg|frame|none|alt=|Stream Isolation Graphic]]

{{project_name_short}} implements protection against {{Code2|identity correlation through Tor circuit sharing}} for preinstalled applications, however, for better privacy, the user is advised to understand a bit of the technical background. Different <code>SocksPort</code>s, <code>DnsPort</code>s, or <code>TransPort</code>s are routed through different Tor circuits, therefore preventing {{Code2|identity correlation}}.

{{project_name_short}} configures most applications that come preinstalled with {{project_name_short}} to use a different <code>SocksPort</code>, thus no {{Code2|identity correlation}} is at risk. {{project_name_short}} uses either socks proxy settings to direct various applications to different <code>SocksPort</code>s or [https://github.com/{{project_name_short}}/uwt uwt] (more information below).

Applications configured for stream isolation (those using a <code>SocksPort</code>) ignore <code>/etc/hosts</code> file. This includes for example [[Tor Browser]]. Therefore modifications to <code>/etc/hosts</code> for the purpose of adblocking are futile (unless using [[Tor_Browser#Tor_Browser_Transparent_Proxying|Tor Browser Transparent Proxying]]).

Application not configured for stream isolation, i.e. those using transparent proxying are usually honoring <code>/etc/hosts</code>. Select applications might have a specific implementation to ignore it depending on the application and unspecific to {{project_name_short}}.

Any other traffic (i.e. custom installed applications, misc applications, such as <code>nslookup</code>, go through Tor's <code>DnsPort</code>, and/or <code>TransPort</code> (can be optionally disabled, see below).

== List ==
Related:

* [[Dev/Default_Application_Policy|{{project_name_short}} Default Application Policy]]
* [https://forums.whonix.org/t/should-strict-stream-isolation-by-a-requirement-in-whonixs-default-application-policy/3940 Should strict stream isolation by a requirement in Whonix's Default Application Policy?]

Applications in {{project_name_short}} that are either prepared or fully pre-configured to prevent {{Code2|identity correlation through Tor circuit sharing}}:

=== By Settings ===
{| class="wikitable" style="text-align: center; background-color: #fff"
!style="height:27px"|application
!pre-installed
!pre-configured
!stream isolation by method
!port
!comments
|-

|style="background-color:#f9f9f9;height:27px"|[[Tor Browser]]
|{{yes}}
|{{yes}}
|[[Tor_Browser/Advanced_Users#Proxy_Settings|socks proxy settings]]
|9150 <ref>{{project_name_workstation_short}} 127.0.0.1:9150 gets redirected to 10.152.152.10:9150 by [https://github.com/Whonix/anon-ws-disable-stacked-tor anon-ws-disable-stacked-tor]. Changing proxy settings in Tor Browser has proven to be unreliable. At some point Tor Button may change its internals and therefore break something again. Keeping the default settings and not requiring any changes in Tor Browser seems like the best way to support compatibility in long run and also is simplest in case {{Code|update-torbrowser}} breaks and [[Tor_Browser/Manual_Download|manually updating Tor Browser]] is required again in future.</ref>
| -
|-

|style="background-color:#f9f9f9;height:27px"|[[E-Mail|Mozilla Thunderbird]]
|{{yes}}
|{{yes}}
|socks proxy settings
|9102
| -
|-

|style="background-color:#f9f9f9;height:27px"|Instant Messenger
|{{no}}
|{{no}}
|socks proxy settings
|port prepared, IP 10.152.152.10, port 9103
|[[Chat]]
|-

|style="background-color:#f9f9f9;height:27px"|[[sdwdate]]
|{{yes}}
|{{yes}}
|socks proxy settings
|9108
|[[Dev/TimeSync]]
|-

|style="background-color:#f9f9f9;height:27px"|[https://www.kicksecure.com/wiki/Systemcheck systemcheck]
|{{Yes}}
|{{yes}}
|socks proxy settings
| 9110
| -
|-

|style="background-color:#f9f9f9;height:27px"|Bitcoin [[electrum]] Wallet (BTC)
|{{Yes}}
|{{no}} ([https://phabricator.whonix.org/T215 TODO])
|socks proxy settings
|port prepared, IP 10.152.152.10, port 9111
| -
|-

|style="background-color:#f9f9f9;height:27px"|[[Monero]] (XMR)
|{{yes}}
|{{no}} ([[Monero#Stream_Isolation|TODO]])
|socks proxy settings
| -
| -
|-

|style="background-color:#f9f9f9;height:27px"|[[Tor_Browser#Tor_Browser_Downloader_by_{{project_name_short}}|Tor Browser Downloader by {{project_name_short}}]]
|{{yes}}
|{{yes}}
|socks proxy settings
|9115
| -
|-

|style="background-color:#f9f9f9;height:27px"|KDE application wide proxy settings
|{{no}}
|{{yes}} <ref>
* https://github.com/Whonix/anon-apps-config/blob/master/etc/profile.d/50_anon-apps-config.sh
* https://github.com/Whonix/anon-apps-config/blob/master/usr/share/anon-apps-config/kioslaverc
</ref>
|socks proxy settings
|9122 no KDE applications with network activity pre-installed
| -
|-

|}

=== By uwt wrapper ===
{| class="wikitable" style="text-align: center; background-color: #fff"
!style="height:27px"|application
!pre-installed
!pre-configured
!stream isolation by method
!port
!comments
|-

|style="background-color:#f9f9f9;height:27px"|apt-get
|style="background-color:{{Green}}"|yes
|style="background-color:{{Green}}"|yes
|uwt wrapper
| -
|[[Update]]
|-

|style="background-color:#f9f9f9;height:27px"|aptitude
|style="background-color:{{Green}}"|yes
|style="background-color:{{Green}}"|yes
|uwt wrapper
| -
| -
|-

|style="background-color:#f9f9f9;height:27px"|gpg
|style="background-color:{{Green}}"|yes
|style="background-color:{{Green}}"|yes
|uwt wrapper
| -
| -
|-

|style="background-color:#f9f9f9;height:27px"|ssh
|style="background-color:{{Green}}"|yes
|style="background-color:{{Green}}"|yes
|uwt wrapper
| -
| -
|-

|style="background-color:#f9f9f9;height:27px"|git
|style="background-color:{{Red}}"|no
|style="background-color:{{Green}}"|yes
|uwt wrapper
| -
| -
|-

|style="background-color:#f9f9f9;height:27px"|wget
|style="background-color:{{Green}}"|yes
|style="background-color:{{Green}}"|yes
|uwt wrapper
| -
| -
|-

|style="background-color:#f9f9f9;height:27px"|curl
|style="background-color:{{Green}}"|yes
|style="background-color:{{Green}}"|yes
|uwt wrapper
| -
| -
|-

|style="background-color:#f9f9f9;height:27px"|scurl
|style="background-color:{{Green}}"|yes
|style="background-color:{{Green}}"|yes
|uwt wrapper
| -
|Uses curl, therefore same as curl.
|-

|}

=== none ===
{| class="wikitable" style="text-align: center; background-color: #fff"
!style="height:27px"|application
!pre-installed
!pre-configured
!stream isolation by method
!port
!instructions
|-

|style="background-color:#f9f9f9;height:27px"|GNOME application wide proxy settings
|style="background-color:{{Red}}"|no
|style="background-color:{{Red}}"|[[Dev/GNOME|no]]
|style="background-color:{{Red}}"|none
|no GNOME applications with network activity pre-installed
| -
|-

|style="background-color:#f9f9f9;height:27px"|<code>[https://www.kicksecure.com/wiki/Systemcheck systemcheck] --leak-tests</code>
|style="background-color:{{Green}}"|yes
|style="background-color:{{Red}}"|no <ref name=systemcheck-leak-tests>
<code>systemcheck --leak-tests</code> runs only on user request and never by its own by chance.

Tests two things, a Tor <code>SocksPort</code> and Tor's <code>TransPort</code>.

<code>SocksPort</code> test uses <code>SOCKS_PORT_SYSTEMCHECK</code> <code>9110</code>.

Stream isolating the transparent proxying, Tor <code>TransPort</code> leak test is impossible. The whole point of the leak test is to check if connections not configured to use a Tor <code>SocksPort</code> will be torified or not.
</ref>
|style="background-color:{{Red}}"|none
|See footnote. <ref name=systemcheck-leak-tests />
| -
|-

|}

== Details ==
The required socks proxy settings are setup by various {{project_name_short}} configuration packages or uwt wrappers, which are set up on {{project_name_gateway_long}} and on {{project_name_workstation_short}}. [https://gitlab.torproject.org/legacy/trac/-/wikis/doc/torsocks uwt] is a wrapper around torsocks, which is also already installed to {{Code|/usr/bin/uwt}}.

* Example, each time you run a uwt wrapped application, i.e. simply type {{Code2|apt-get}} in console, the uwt wrapper {{Code|/usr/bin/apt-get}} will run. It adds uwt before apt-get. For curiosity check {{Code|nano /usr/bin/apt-get}}. Essentially, the uwt wrapper then runs {{Code|/usr/bin/uwt /usr/bin/apt-get.anondist-orig}}. That is also the case for all other uwt wrapped applications.
* If you ever want or must run a uwt wrapped application without uwt, do not run for example {{Code|apt-get}} in console, do run {{Code|apt-get.anondist-orig}}. Use cases could be if you want to connect to localhost. If you know what you are doing, you should also be able to deactivate any uwt wrappers you dislike, see [[#Deactivate_uwt_Stream_Isolation_Wrapper]].
* When running {{Code2|/usr/bin/apt-get.anondist-orig}} it directly goes through Tor's <code>DnsPort</code> and through Tor's <code>TransPort</code> and not through its own <code>SocksPort</code>.
* uwt looks if the command contains the words {{Code2|localhost}} or {{Code2|127.0.0.1}}, if that is the case, uwt will not be used. The command will be run without uwt. Thus, if a localhost connection is falsely detected it will leak, but only through Tor's <code>DnsPort</code> and through Tor's <code>TransPort</code>, which should be acceptable.

Isolate by destination address: Let's assume SSH goes over port 22 and you want to connect to different SSH servers and do not want an observer to be able to correlate that activity to the same pseudonym. If the SSH servers run on different IP's isolate by destination address might help.

Isolate by destination port: This doesn't seem to be useful for anything in {{project_name_short}}, applications using different protocols (and therefore different ports) are already isolated through using different <code>SocksPort</code>s.

Isolate by destination port doesn't really achieve anything for web browsing: [https://lists.torproject.org/pipermail/tor-talk/2012-May/024403.html tor-talk Tor's stream isolation features defaults].

For more information about stream isolation refer to the Tor manual.

* [https://2019.www.torproject.org/docs/tor-manual.html.en Tor stable manual]
* [https://2019.www.torproject.org/docs/tor-manual-dev.html.en Tor alpha manual]

Different tabs and websites in Tor Browser are isolated by since Tor Browser. <ref>
https://gitlab.torproject.org/legacy/trac/-/issues/3455
</ref>

Connections to different Tor [[Onion Services]] are automatically stream isolated. <ref>
https://lists.torproject.org/pipermail/tor-talk/2012-September/025432.html
</ref>

== How to mitigate identity correlation ==
=== Basic Protection ===
If you install custom software on {{project_name_workstation_short}}, that uses the internet, and want to prevent {{Code2|identity correlation through Tor circuit sharing}} (which you should do), you have to manually configure them. This is not a {{project_name_short}} specific problem. <ref>
If you used to use only one <code>SocksPort</code> with the [https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TorifyHOWTO common torification methods], the [https://lists.torproject.org/pipermail/tor-talk/2012-March/023535.html same thing happened].
</ref> Read also [[Install Software|Software installation on {{project_name_workstation_short}}]].

A [[#list]] of applications which come pre-installed with {{project_name_short}} are pre-configured to prevent {{Code2|identity correlation through circuit sharing}}.

Traffic going through <code>TransPort</code> by default is [https://www.kicksecure.com/wiki/Systemcheck systemcheck] when manually testing the <code>TransPort</code> by using <code>systemcheck --leak-tests</code>. If that is of concern to you,

* It can be disabled in systemcheck, see [https://www.kicksecure.com/wiki/Systemcheck_Hardening#Prevent_Polluting_TransPort prevent polluting <code>TransPort</code>] but that might make little sense.
* Better to avoid the test instead.

All custom installed application's TCP traffic is routed through Tor's <code>TransPort</code> and all their DNS requests through Tor's <code>DnsPort</code>. This means different activities or "identities" in different applications (say browser, IRC, email) end up being routed through the same Tor circuit, thus {{Code2|identity correlation}} is at risk. <ref>
What about UDP? See [[Tor#UDP]].
</ref>

To protect against this, you have to set up configure applications to use a dedicated Tor <code>SocksPort</code>. Each custom installed application has to be directed to a dedicated Tor <code>SocksPort</code>, for directions how to do that use the [https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TorifyHOWTO Torify HOWTO]. Generally, this can be done either by configuring the application's proxy settings or by using a proxifier (socksifier) such as <code>torsocks</code>.

[[Multiple Whonix-Workstation|Multiple {{project_name_workstation_short}}]] are automatically stream isolated. <ref name=multiple-workstation />

What is better, configure the application's proxy settings or using a proxifier? There can be no generalized answer as this is highly application specific. The most comprehensive documentation of this is the Torify HOWTO. Also a web search could be performed on how to torify applications.

Applications inside {{project_name_short}} are already torified but by applying these instructions inside {{project_name_short}} the user would go one step further, i.e. add stream isolation.

Finding up to date instructions for torification is difficult because developing instructions for torification itself is a difficult process. Someone who understands networking needs to leak test if the torification instructions are actually working. Or if there is a leak which means that portion's of the applications's traffic ignore proxy settings and/or circumvent the proxifier and is actually making external connections without using Tor. Such leaks would be much less severe in {{project_name_short}}. It would only result in {{Code2|identity correlation through Tor circuit sharing}} but not in a leak of the user's real IP address to the destination.

Asking for torification instructions for specific applications at {{project_name_short}} [[Support|Free Support]] is probably futile unless it is a [[Premium Support|premium support request]]. The {{project_name_short}} is the wrong recipient for such support requests. One of the main reasons for the inception of the {{project_name_short}} was that finding, developing and applying torification instructions is so difficult and one never really knows if it is 100% free of leaks. Even seriously reviewed torification instructions for one application would only apply to the very version which was being reviewed. Not to future versions of the application.

The legacy approach of torification of arbitrary applications on the host seems to been largely given up. There are very few edits to the Torify HOWTO over the years. Nowadays some application developers are providing Tor-safe by default applications, i.e. applications designed for use with Tor in mind and not as an afterthought. Examples include [[Tor Browser]] and [[OnionShare]]. Also if users are asking how to torifiy specific applications and making sure these are leak free, users are probably told "use Whonix".

Additional comments regarding the Torify HOWTO:

* Warnings about protocol related warnings you must honor. You are still better off with {{project_name_short}}, as it offers best possible [[Protocol-Leak-Protection and Fingerprinting-Protection]].
* {{project_name_short}} setup provides protection against IP leaks through [https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TorifyHOWTO#protocol-leaks protocol leaks].
* If you do not correctly torify either no connections will be possible or traffic will either continue going through Tor's <code>TransPort</code> unless you [[#Better Protection|disable transparent torification]].
* If you redirect more than one application to the same <code>SocksPort</code>, {{Code2|identity correlation}} is at risk.
* DNS related [https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TorFAQ#i-keep-seeing-these-warnings-about-socks-and-dns-and-information-leaks-should-i-worry warnings] still apply, though to a lesser extent - an attack could only make correlations but still couldn't figure out your IP. To prevent that see chapter [[#Better Protection|better protection]].
** Do not use a [https://gitlab.torproject.org/legacy/trac/-/wikis/doc/SupportPrograms#dns-resolvers local DNS resolver], as all DNS requests would be executed by the same Tor circuit.
* Other leaks, such as applications not honoring the proxy settings / wrapper, ICMP or UDP leaks do not apply to {{project_name_short}}.
* The SafeSocks setting is for rejecting unsafe variants of socks that might cause DNS leaks. The {{project_name_short}} design model mitigates DNS leaks by redirecting all requests to Tor's <code>DnsPort</code>. Enabling this setting would give marginal benefit in this situation but would complicate debugging.

On {{project_name_gateway_short}} there are already a lot custom socks ports prepared for use with custom installed applications <ref>
Tor configuration file <code>/etc/torrc.d/70_workstation.conf</code> <code>%include</code>s file <code>/usr/share/tor/tor-service-defaults-torrc.anondist</code>.
</ref>:

* Without {{Code2|IsolateDestAddr}} and without {{Code2|IsolateDestPort}}: <code>SocksPort</code> <code>9153</code> to <code>9159</code>
* With {{Code2|IsolateDestAddr}}, but without {{Code2|IsolateDestPort}}: <code>SocksPort</code> <code>9160</code> to <code>9169</code>
* Without {{Code2|IsolateDestAddr}}, but with {{Code2|IsolateDestPort}}: <code>SocksPort</code>: <code>9170</code> to <code>9179</code>
* With {{Code2|IsolateDestAddr}} and with {{Code2|IsolateDestPort}}: <code>SocksPort</code>: <code>9180</code> to <code>9189</code>
* If those are not enough, you can add your own.

What are {{Code2|IsolateDestAddr}} and {{Code2|IsolateDestPort}}? You can learn about them in the [https://2019.www.torproject.org/docs/tor-manual.html.en Tor manual]. See also [https://lists.torproject.org/pipermail/tor-talk/2012-May/024403.html tor-talk mailing list: Tor's stream isolation features defaults]. Usually, unless you know better, you are better off not using {{Code2|IsolateDestAddr}} or {{Code2|IsolateDestPort}}.

{{Box|text=
'''Generic instructions for configuring custom installed applications for stream isolation for less than 7 custom applications'''

# [[Install Software|Install]] custom application.
# Configure application to use a dedicated Tor <code>SocksPort</code> according to [https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TorifyHOWTO Torify HOWTO] by either configuring the application's proxy settings or by using a proxifier such as <code>torsocks</code>.
# Start custom application.
}}

{{Box|text=
'''Generic instructions for configuring custom installed applications for stream isolation using proxifier (socksifier) <code>torsocks</code>'''

# [[Install Software|Install]] custom application.
# {{Open a product ws terminal}}
3. Start custom application from command line by prepending <code>torsocks</code>.

{{CodeSelect|code=
torsocks application-name
}}

Using this method, there is no need to specify any proxy IP address, port number, protocol. <ref>
This is because <code>torsocks</code> configuration file [https://github.com/{{project_name_short}}/uwt/blob/master/etc/tor/torsocks.conf.anondist <code>/etc/tor/torsocks.conf.anondist</code>] is preconfigured with setting <code>IsolatePID 1</code>.

<pre>
# Set Torsocks to use an automatically generated SOCKS5 username/password based
# on the process ID and current time, that makes the connections to Tor use a
# different circuit from other existing streams in Tor on a per-process basis.
# If set, the SOCKS5Username and SOCKS5Password options must not be set.
# (Default: 0)
IsolatePID 1
</pre>
</ref>
}}

{{Box|text=
'''Generic instructions for configuring custom installed applications for stream isolation for less than 7 custom applications using the application's proxy settings'''

# [[Install Software|Install]] custom application.
# Configure application to use a dedicated Tor <code>SocksPort</code> according to [https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TorifyHOWTO Torify HOWTO] by either configuring the application's proxy settings.
# protocol: socks 5
# Platform specific. [[Non-Qubes-Whonix]] proxy IP: {{CodeSelect|code=10.152.152.10}} Qubes-Whonix: Use the IP address returned by running the following command (NOTE: do not use the command itself): {{CodeSelect|code=qubesdb-read /qubes-gateway}}
# port: {{CodeSelect|code=9153}} (use a different port according to list above if using multiple custom installed applications)
# Start custom application.

Better generic instructions for this cannot be provided since this is application specific as mentioned above.
}}

=== Better Protection ===
For best protection against {{Code2|identity correlation}}:

* Read the advice above and on {{project_name_gateway_short}}.
* Deactivate KDE / GNOME - application wide proxy settings because those proxy settings are not application specific, but rather force all KDE / GNOME applications through the same <code>SocksPort</code>. There no KDE / GNOME applications which use the internet preinstalled by default. However, deactivating those KDE / GNOME wide proxy settings gives finer control over stream isolation.
* Disable transparent proxying as documented below.

=== Best Protection ===
Best stream isolation is only possible if you honor the advice above and only use one application per session and always revert to a fresh image or [[Multiple Whonix-Workstation|Multiple {{project_name_workstation_short}}]]. <ref name=multiple-workstation>
[[Multiple Whonix-Workstation|Multiple {{project_name_workstation_short}}]] using different internal IP's are automatically separated by Tor (<code>IsolateClientAddr</code> is Tor's default).
</ref>

=== Disable Transparent Proxying ===
To deactivate transparent proxying apply the following instructions.

Following these steps will disable the {{project_name_gateway_short}} [[#Transparent Proxy|transparent proxying]] feature and transform {{project_name_gateway_short}} into an [https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TorifyHOWTO/IsolatingProxy IsolatingProxy].

'''Note:''' The following instructions should be applied in {{project_name_gateway_short}} ([[Qubes|{{q_project_name_long}}]]: In App Qubes <code>{{project_name_gateway_vm}}</code>).

'''1.''' {{Firewall_Settings}}

'''2.''' Add.

{{CodeSelect|code=
WORKSTATION_TRANSPARENT_TCP=0
WORKSTATION_TRANSPARENT_DNS=0
}}

'''3.''' Save.

'''4.''' {{Reload_Firewall}}

<ref>
Although not strictly required, you could alternatively/additionally deactivate Tor <code>TransPort</code> and <code>DnsPort</code>.

Add to {{Code2|/usr/local/etc/torrc.d/50_user.conf}}.

{{Open /usr/local/etc/torrc.d/50_user.conf}}

Add.

{{CodeSelect|code=
TransPort 0
DnsPort 0
}}

Save.

And then {{Reload_Tor}}
</ref>

'''5.''' Done.

Deactivating transparent proxying is complete.

This will disable transparent proxying. All applications not configured to use a <code>SocksPort</code> by socks proxy settings or forced to use a <code>SocksPort</code> by a socksifier will not be able to establish connections. This is the only way to ensure that different <code>SocksPort</code>s are used and also that DNS is remotely resolved through that <code>SocksPort</code>.

'''6.''' Test.

Optional.

* [[#Check if Transparent DNS is disabled|Check if Transparent DNS is disabled]]
* [[#Check if Transparent TCP is disabled|Check if Transparent TCP is disabled]]

=== IsolateSOCKSAuth ===
See [https://2019.www.torproject.org/docs/tor-manual.html.en Tor manual] <code>IsolateSOCKSAuth</code>.

<blockquote>Don’t share circuits with streams for which different SOCKS authentication was provided. [...]</blockquote>

== Deactivate Stream Isolation ==
=== Easy ===
Choose an option. Either '''A)''' or '''B)'''.

* '''A)''' [[Stream_Isolation/Disable_Easy|How to disable stream isolation. Most easy and common methods only.]] Or,
* '''B)''' For more options, see below.

=== Deactivate uwt Stream Isolation Wrapper ===
'''OPTIONAL. Usually not required. Only for special setups and people who know what they are doing.'''

==== Temporary ====
===== anondist-orig Method =====
Append {{Code2|.anondist-orig}} to the command you want to run. For example, instead of using.

{{CodeSelect|code=
curl 38.229.72.22
}}

Use.

{{CodeSelect|code=
curl.anondist-orig 38.229.72.22
}}

===== Environment Variable Method =====
Use the {{Code2|UWT_DEV_PASSTHROUGH}} environment variable. <ref>https://github.com/{{project_name_short}}/uwt/blob/master/usr/libexec/uwt/uwtwrapper#L194</ref>

Example. Set the UWT_DEV_PASSTHROUGH environment variable. This will disable using <code>torsocks</code> for all following invocations.

{{CodeSelect|code=
export UWT_DEV_PASSTHROUGH="1"
}}
{{CodeSelect|code=
curl 38.229.72.22
}}

When running as user and using <code>sudo</code>, do not forget <code>sudo</code> parameter <code>-E</code> which stands for preserve environment.

{{CodeSelect|code=
sudo -E apt update
}}

==== Permanently ====
===== Introduction =====
You can enable/disable all uwt stream isolation wrappers globally or enable/disable specific stream isolation wrappers, see uwt <code>/etc/uwt.d/30_uwt_default.conf</code> configuration file.

===== deactivate all uwt wrappers permanently =====
{{Uwt_wrappers_deactivate_all_permanently}}

=== Deactivate Misc Proxy Settings ===
{{Deactivate_Misc_Proxy_Settings}}

=== Tor Browser Remove Proxy Settings ===
If you would like to remove proxy settings from Tor Browser, see below.
{{Tor_Browser_Remove_Proxy_Settings}}

== Nested Execution ==
uwt version <code>4.0-1</code> and above protects form endless nested execution which could likely lead to a locked up session by aborting after 10 times an uwt wrapped application calling another uwt wrapped application. In that case, you would see the following error message.

<blockquote>
uwtwrapper uwt wrapper ERROR: More than uwtwrapper_counter 10 nested executions (uwtwrapper_max: 10).
</blockquote>

This is most likely happening due to two symlinks pointing to each other resulting in endless execution. However, should there be any cases (none could be foreseen at development time) where this is legitimate, feel free to change the setting responsible for aborting execution. Please also consider reporting your use case in {{project_name_short}} forums so perhaps a better fix for this can be found.

{{Open with root rights|filename=
/etc/uwt.d/50_user.conf
}}

Set <code>uwtwrapper_max</code> to a value more suitable for you.

{{CodeSelect|code=
uwtwrapper_max=100
}}

Alternatively you could completely disable the nested execution protection.

{{CodeSelect|code=
nested_protection() {
    true
}
}}

Save and exit.

Done.

== Development ==
=== Information ===
See also the [https://2019.www.torproject.org/docs/tor-manual.html.en Tor manual] on <code>SocksPort</code>, <code>HTTPTunnelPort</code>, <code>TransPort</code> and <code>DnsPort</code>.

==== SocksPort ====
A <code>SocksPort</code> is a listen port by Tor which accepts traffic using the [https://en.wikipedia.org/wiki/SOCKS socks] protocol.

Using a <code>SocksPort</code> is possible by using either:

* [https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TorifyHOWTO#Classicalcommonway:usetheapplicationsproxysettings application specific socks proxy settings]
* [https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TorifyHOWTO#classical-common-way-use-the-applications-proxy-settings wrapper method] such as <code>torsocks</code> (which can be automatically prepended using [https://github.com/{{project_name_short}}/uwt <code>uwt</code>]

Traffic on separate <code>SocksPort</code>s is stream isolated by Tor default.

==== HTTPTunnelPort ====
A <code>HTTPTunnelPort</code> is a listen port by Tor which accepts traffic using the [https://en.wikipedia.org/wiki/HTTP_tunnel HTTP CONNECT method].

This is a new feature of Tor.

Traffic on separate <code>HTTPTunnelPort</code>s is stream isolated by Tor default.

Forum discussion:<br />
https://forums.whonix.org/t/tor-can-now-serve-as-http-proxy-httptunnelport/5373

==== TransPort ====
<code>TransPort</code> is a feature where Tor accepts raw traffic on a listen port if redirected there using iptables. See also [https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TransparentProxy TransparentProxy].

When using Transparent Proxying (default in {{project_name_short}}) (see this page for Transparent Proxying for more information), all applications that do not use a <code>SocksPort</code> or <code>HTTPTunnelPort</code> will fall back to be using Tor's <code>TransPort</code> for TCP. I.e. using system default networking. This is also called transparent proxying.

There is no stream isolation for <code>TransPort</code> connections unless originating from a [[Multiple Whonix-Workstation|separate {{project_name_workstation_short}}]]. <ref name=multiple-workstation/>

==== DnsPort ====
Similar to above but for DNS. All applications that do not use a <code>SocksPort</code> or <code>HTTPTunnelPort</code> will fall back to be using Tor's <code>DnsPort</code> for DNS.

==== torsocks ====
All [[Stream_Isolation#By_uwt_wrapper|uwt wrapped applications]] will be stream isolated by [https://github.com/{{project_name_short}}/uwt/blob/master/etc/tor/torsocks.conf.anondist <code>torsocks</code>] <code>/etc/tor/torsocks.conf</code> setting <code>IsolatePID 1</code>.

To test this, run multiple times the following command.

<pre>
scurl https://check.torproject.org | grep IP
</pre>

=== Tests ===
1. Applications which internally use curl.

{{CodeSelect|code=
sudo update-command-not-found
}}
{{CodeSelect|code=
sudo update-flashplugin-nonfree --install --verbose
}}

2. Applications which is uwt wrapped itself and internally uses ssh.

{{CodeSelect|code=
git push origin master
}}

3. Enigmail.

=== Debugging / List of all uwt wrappers ===
{{CodeSelect|code=
sudo dpkg-divert --list
}}
{{CodeSelect|code=
ls -la /usr/bin/ssh
}}

=== Deactivating an uwt wrapper ===
Example:

{{CodeSelect|code=
sudo unlink /usr/bin/ssh
}}
{{CodeSelect|code=
sudo dpkg-divert --rename --remove /usr/bin/ssh
}}

=== Check if Transparent DNS is disabled ===
'''Note:''' The following test should be performend in {{project_name_workstation_short}} ([[Qubes|{{q_project_name_short}}]]: App Qube <code>{{project_name_workstation_vm}}</code>).

Test.

{{CodeSelect|code=
nslookup check.torproject.org ; echo $?
}}

Expected output.

<pre>
;; connection timed out; no servers could be reached

1
</pre>

If it shows something else, such as a resolved IP, the Transparent DNS is enabled.

=== Check if Transparent TCP is disabled ===
'''Note:''' The following test should be performend in {{project_name_workstation_short}} ([[Qubes|{{q_project_name_short}}]]: App Qube <code>{{project_name_workstation_vm}}</code>).

Test.

{{CodeSelect|code=
{{Curl_Plain}} {{Check.torproject.org IP}} ; echo $?
}}

Expected output.

<pre>
curl: (7) couldn't connect to host
7
</pre>

If it shows something else, such as the html source code, then Transparent TCP is enabled.

=== Check if Transparent Proxying is disabled ===
'''Note:''' The following test should be performend in {{project_name_workstation_short}} ([[Qubes|{{q_project_name_short}}]]: App Qube <code>{{project_name_workstation_vm}}</code>).

Test.

{{CodeSelect|code=
{{Curl_Plain}} https://check.torproject.org/ ; echo $?
}}

Expected output.

<pre>
curl: (6) Couldn't resolve host 'check.torproject.org'
6
</pre>

If it shows something else, such as the html source code, then Transparent Proxying is enabled.

=== Check if an Application is properly using Stream Isolation ===
* Same as <code>leak testing</code> as if {{project_name_short}} is not involved.
* Also... A weaker test... The <code>transparent proxying disablement</code> test.

Disable transparent proxying of DNS and TCP as per [[#Better Protection]].

Check that worked as per:

* [[#Check if Transparent DNS is disabled|Check if Transparent DNS is disabled]]
* [[#Check if Transparent TCP is disabled|Check if Transparent TCP is disabled]]

That is because it doesn't work without transparent proxying (system default networking), meaning application unable to use network normally, then there is a certain socks leak, meaning certainly some traffic which requires system default networking. In case of:

* clearnet operating systems: a clearnet leak
* {{project_name_short}}: a stream isolation violation

This is only weak test since an application could very likely try socks first and if socks fails, fall back to system default networking. Therefore, normal <code>leak testing</code> is required.

* Internet research if application was specifically designed for use with Tor.
* Internet research if application was specifically audited for clearnet leaks.
* Discussion with software contributor about this if these haven't already happened.
* https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TorifyHOWTO#Howtoreviewanapplication
* https://lists.torproject.org/pipermail/tor-talk/2012-April/024010.html
* https://gitlab.torproject.org/legacy/trac/-/issues/5553
* [https://github.com/rustybird/corridor corridor - Tor traffic whitelisting gateway]

=== Add new uwt wrapper ===
Emulate [https://github.com/{{project_name_short}}/uwt/commit/03cc4c8568564d5993fcc8ea975cf00e851f7052 this commit].

== Sources ==

* [https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/171-separate-streams.txt Separate streams across circuits by connection metadata]
* [https://lists.torproject.org/pipermail/tor-talk/2012-March/023496.html tor-talk Operating system updates / software installation behind Tor Transparent Proxy]
* [https://lists.torproject.org/pipermail/tor-talk/2012-March/023536.html tor-talk Awareness for identity correlation through circuit sharing is almost zero.]
* [https://lists.torproject.org/pipermail/tor-talk/2012-May/024401.html tor-talk Tor's stream isolation features defaults Question]
* [https://lists.torproject.org/pipermail/tor-talk/2012-May/024403.html tor-talk Tor's stream isolation features defaults Answer]
* [https://web.archive.org/web/20141005211329/https://mailman.boum.org/pipermail/tails-dev/2012-August/001422.html Tails-dev separate Tor streams]
* [https://tails.boum.org/todo/separate_Tor_streams/ Tails separate Tor streams]
* [https://web.archive.org/web/20160629092058/https://mailman.boum.org/pipermail/tails-dev/2012-August/001532.html Tails-dev Please review Tails stream isolation plans]
* [https://tails.boum.org/contribute/design/stream_isolation/ Tails Design: Tor stream isolation]

Stream Isolation Graphic has been contributed by: Cuan Knaggs – graphic and web design [https://web.archive.org/web/20160313102442/http://revolver.za.net/ revolver] print media – web design – web development – cms – e-commerce

== References ==
{{reflist|close=1}}

{{Footer}}

[[Category:Documentation]] [[Category:Design]]