[tor-bugs] #3455 [Tor Browser]: Tor Browser should set SOCKS username for a request based on referer

[Tor Bug Tracker & Wiki]

#3455: Tor Browser should set SOCKS username for a request based on referer
-------------------------+--------------------------------------------------
 Reporter:  mikeperry    |          Owner:  mikeperry
     Type:  enhancement  |         Status:  new      
 Priority:  major        |      Milestone:           
Component:  Tor Browser  |        Version:           
 Keywords:               |         Parent:           
   Points:               |   Actualpoints:           
-------------------------+--------------------------------------------------

Comment(by rransom):

 Replying to [ticket:3455 mikeperry]:
 > Once Proposal 171 is implemented (#1865), Tor Browser should set the
 Proposal 171 SOCKS username to a function of the hostname in the referer
 header (possibly caching the first referer for subsequent link
 navigation).

 The SOCKS password would be a better field for intra-application identity
 compartments, so that when Tor decides to shove two compartments into the
 same circuit, it can merge two compartments run by the same application
 together before it merges different applications' compartments (which
 could have different SOCKS usernames) together.

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