[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #17359 [Core Tor/Tor]: __DisablePredictedCircuits causes bootstrap to hang at "Connecting to Tor Network"
#17359: __DisablePredictedCircuits causes bootstrap to hang at "Connecting to Tor
Network"
---------------------------------------------+-----------------------------
Reporter: teor | Owner: (none)
Type: defect | Status: new
Priority: Low | Milestone: Tor:
| unspecified
Component: Core Tor/Tor | Version:
Severity: Minor | Resolution:
Keywords: tor-hs bootstrap sponsor8-maybe | Actual Points:
Parent ID: | Points: small
Reviewer: | Sponsor:
---------------------------------------------+-----------------------------
Description changed by arma:
Old description:
> When __DisablePredictedCircuits is set in the torrc, bootstrap hangs at
> 80% - "Connecting to Tor Network".
>
> This happens in hidden service configurations, it may happen in other
> client or server configurations as well.
>
> I think this is because:
> * no predicted circuits are being built, and therefore
> * tor never completes an OR connection, and therefore
> * tor never thinks it has bootstrapped, and therefore
> * tor doesn't make any of the OR connections it would make as part of its
> configured function
>
> To fix this, we need to either:
> * assume tor is connected to the network if it gets to "Connecting to Tor
> Network" and __DisablePredictedCircuits is set, or
> * make at least one connection at "Connecting to Tor Network" even if
> __DisablePredictedCircuits is set
>
> The first risks repeatedly making connections if tor isn't connected to
> the network, the second risks making connections the user doesn't want.
New description:
When {{{__DisablePredictedCircuits}}} is set in the torrc, bootstrap hangs
at 80% - "Connecting to Tor Network".
This happens in hidden service configurations, it may happen in other
client or server configurations as well.
I think this is because:
* no predicted circuits are being built, and therefore
* tor never completes an OR connection, and therefore
* tor never thinks it has bootstrapped, and therefore
* tor doesn't make any of the OR connections it would make as part of its
configured function
To fix this, we need to either:
* assume tor is connected to the network if it gets to "Connecting to Tor
Network" and {{{__DisablePredictedCircuits}}} is set, or
* make at least one connection at "Connecting to Tor Network" even if
{{{__DisablePredictedCircuits}}} is set
The first risks repeatedly making connections if tor isn't connected to
the network, the second risks making connections the user doesn't want.
--
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17359#comment:17>
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