[tor-bugs] #14382 [Tor Messenger]: enable Stream Isolation

[Tor Bug Tracker & Wiki]

#14382: enable Stream Isolation
-------------------------------+-----------------
     Reporter:  proper         |      Owner:
         Type:  defect         |     Status:  new
     Priority:  normal         |  Milestone:
    Component:  Tor Messenger  |    Version:
   Resolution:                 |   Keywords:
Actual Points:                 |  Parent ID:
       Points:                 |
-------------------------------+-----------------

Comment (by yawning):

 Per IRC:
 {{{
 06:22:04      armadev | sukhe: huh! hm. what are the arguments for and
 against?
 06:22:23      armadev | i guess 'for' includes 'you shouldn't mix your
 protocols
                       | onto the same circuit, and besides tor messenger
 doesn't
                       | produce that many streams anyway'?
 06:22:42      armadev | and 'against' includes 'what if somebody runs tor
                       | messenger to have a generic socksport, and then
 they
                       | hook their other app up to it?'
 }}}

 The approach I suggest requires adding code (and isn't as straightforward
 as just enabling 2 config options and being done with it) would be to use
 the `IsolateSOCKSAuth` option, enabled by default to accomplish this.  It
 would be up to the application (in this case Tor Messenger) to logically
 group related SOCKS connections together by means of the authentication
 information provided, but it gives the app more fine grained control over
 how Tor will isolate things, and won't have any unintended sideeffects.

 The drawback to using `IsolateSOCKSAuth` is that it requires writing the
 app side code to do this, but maybe the Tor Browser people have
 suggestions in that area.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/14382#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online