[tor-bugs] #28281 [Core Tor/Tor]: outline of high-level bootstrap tracker abstractions

Tor Bug Tracker & Wiki blackhole at torproject.org
Fri Nov 30 20:07:39 UTC 2018


#28281: outline of high-level bootstrap tracker abstractions
--------------------------+------------------------------------
 Reporter:  catalyst      |          Owner:  catalyst
     Type:  task          |         Status:  assigned
 Priority:  Medium        |      Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:  s8-boostrap   |  Actual Points:
Parent ID:  #28018        |         Points:  0.5
 Reviewer:                |        Sponsor:  Sponsor8
--------------------------+------------------------------------

Comment (by catalyst):

 I thought about this a bit more, and I think we might want to disambiguate
 the connection progress messages a bit.  We probably shouldn't always
 report the first TCP connection the same way, because it means something
 different to the user if the TCP connection to the first proxy fails,
 compared to if the TCP connection to the first relay fails.  So we
 shouldn't use the raw connection progress indications from the ORCONN code
 without decoding them first a bit.

 I think if we know we're connecting through a proxy, we should report the
 first TCP connection as something like `proxy_connecting` and
 `proxy_connected`.  But then this gets confusingly named with the proxy
 handling code in connection.c that talks the proxy protocol and makes
 connection requests to the proxy.  Maybe we should report the progress of
 asking the proxy to make the relay connection as `connecting` and
 `connected`?

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


More information about the tor-bugs mailing list