[tor-bugs] #18859 [Core Tor]: A new SOCKS connection should use a pre-built circuit for its stream

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#18859: A new SOCKS connection should use a pre-built circuit for its stream
---------------------------------+-----------------
     Reporter:  arthuredelstein  |      Owner:
         Type:  defect           |     Status:  new
     Priority:  Medium           |  Milestone:
    Component:  Core Tor         |    Version:
     Severity:  Normal           |   Keywords:
Actual Points:                   |  Parent ID:
       Points:                   |   Reviewer:
      Sponsor:                   |
---------------------------------+-----------------
 Since #3455, we use SOCKS auth isolation in Tor Browser to separate URL
 bar domains to different tor circuits. When the user browses to a new URL
 bar domain, a new SOCKS connection is opened with a SOCKS
 username/password unique to the site's domain.

 By telneting to the tor control port, I observed that immediately after I
 entered a new URL bar domain in a Tor Browser tab, a new circuit was built
 and assigned the SOCK_USERNAME and SOCKS_PASSWORD for that URL bar domain.

 It seems there would be better performance if we could use an existing,
 pre-built (yet-unused) circuit when a new SOCKS connection opens, and
 assign the SOCKS_USERNAME and SOCKS_PASSWORD to the pre-built circuit.
 That way the user wouldn't have to wait for a circuit to be established
 after requesting a new website.

 I don't know yet whether this is something that can be adjusted by config
 settings or if we would need to patch tor somehow.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18859>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs