[tor-bugs] #3455 [Firefox Patch Issues]: Tor Browser should set SOCKS username for a request based on first party domain

[Tor Bug Tracker & Wiki]

#3455: Tor Browser should set SOCKS username for a request based  on first party
domain
-------------------------------------+-------------------------------------
     Reporter:  mikeperry            |      Owner:  mikeperry
         Type:  enhancement          |     Status:  needs_information
     Priority:  major                |  Milestone:  TorBrowserBundle
    Component:  Firefox Patch        |  2.3.x-stable
  Issues                             |    Version:
   Resolution:                       |   Keywords:  tbb-linkability, tbb-
Actual Points:                       |  usability
       Points:                       |  Parent ID:  #5752
-------------------------------------+-------------------------------------

Comment (by anon):

 As mentioned users with a local firewall have to punch holes for specific
 reasons already. Rather than assuming that a handful is acceptable but a
 few more is not, consider a auto port range setting.

 Thus users would specify a local ephemeral or dynamic range of ports for
 Tor (ex. 9000 to 9999) or by process (Tor.exe) to whitelist in their local
 network policy authority.

 Where this becomes a problem is with Unix domain sockets like SocksSocket;
 creating these dynamically may need a parent directory or other tmpfile
 like collision resistant method to support multiple unix domain socket
 paths. See https://trac.torproject.org/projects/tor/ticket/12585

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