Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:06:49Zhttps://gitlab.torproject.org/legacy/trac/-/issues/21594Hidden Services with many intro points delay checking circuits on startup2020-06-13T15:06:49ZteorHidden Services with many intro points delay checking circuits on startupWhen a hidden service with 8-10 introduction points starts, it delays checking for failed circuits for 5 minutes.
Fixes part of issue 1 in #21446.When a hidden service with 8-10 introduction points starts, it delays checking for failed circuits for 5 minutes.
Fixes part of issue 1 in #21446.Tor: 0.3.0.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/21598Log a message when a hidden service has fewer introduction points than expected2020-06-13T15:06:51ZteorLog a message when a hidden service has fewer introduction points than expectedDiagnostic for bugs like #21446.Diagnostic for bugs like #21446.Tor: 0.3.1.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/21599Make hidden service descriptor creation more consistent2020-06-13T15:06:51ZteorMake hidden service descriptor creation more consistentThis cleans up #21596: now that circuit_established is reliable, it can be used during descriptor creation as well. This prevents a regression to bugs like #21594.This cleans up #21596: now that circuit_established is reliable, it can be used during descriptor creation as well. This prevents a regression to bugs like #21594.Tor: 0.3.1.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/21600Hidden service introduction point retries occur at 1 second intervals2020-06-13T15:06:52ZteorHidden service introduction point retries occur at 1 second intervalsTor will try to reconnect to an introduction point up to 3 times.
But rend_consider_services_intro_points() is called every second, which means that it uses up these retries very quickly, particularly if the connection fails quickly, lik...Tor will try to reconnect to an introduction point up to 3 times.
But rend_consider_services_intro_points() is called every second, which means that it uses up these retries very quickly, particularly if the connection fails quickly, like direct connections sometimes do on single onion services.
It might be more sensible to retry slightly more slowly.
On the other hand, maybe it's good that we fail fast and replace the introduction point.
This behaviour was introduced in commit 1125a4876b4.Tor: unspecifiedGeorge KadianakisGeorge Kadianakishttps://gitlab.torproject.org/legacy/trac/-/issues/21622Log a message when a hidden service delays new introduction point circuits2020-06-13T15:06:55ZteorLog a message when a hidden service delays new introduction point circuitsWhen a hidden service stops making new introduction point circuits, it would be useful to log a message saying:
* how many connections it has made so far,
* how long it took it to make those connections,
* what the connection limit is,
*...When a hidden service stops making new introduction point circuits, it would be useful to log a message saying:
* how many connections it has made so far,
* how long it took it to make those connections,
* what the connection limit is,
* in what time that many connections can be made, and
* a list of the current intro point connections.
This is a follow-up to #21599.Tor: 0.3.1.x-finalteorteor