[tor-bugs] #4483 [Tor]: If k of n authorities are down, k/n bootstrapping clients are delayed for minutes
Tor Bug Tracker & Wiki
blackhole at torproject.org
Sun Dec 13 09:42:39 UTC 2015
#4483: If k of n authorities are down, k/n bootstrapping clients are delayed for
minutes
-------------------------------------------------+-------------------------
Reporter: arma | Owner: teor
Type: defect | Status:
Priority: High | needs_review
Component: Tor | Milestone: Tor:
Severity: Normal | 0.2.8.x-final
Keywords: performance, bootstrap, dirauth- | Version:
dos-resistance, tor-client, large-feature, | Resolution:
prop210, 028-triage, TorCoreTeam201512, | Actual Points:
MikePerry201512R | Points:
Parent ID: #2664 | medium/large
Sponsor: SponsorU |
-------------------------------------------------+-------------------------
Comment (by nickm):
bc8f21f7bd4ed3ea52da94f44c58f34919841307 (Add attempt-based connection
schedules)
* download_status_schedule_helper dereferences dls before it does
tor_assert(dls); coverity won't like that, I think.
* download_status_schedule_helper seems like a bad name. It doesn't
have a verb. Maybe it should be ..._get_interval?
* Somewhere, we need to explain how a dls actually works -- what it
means, how to interpret it. I don't think the documentation in or.h
really explains. Honestly, I'm not sure how this commit '''works'''. I
think that an expanded comment on download_schedule_t type might be in
order.
* good to see tests though.
3244f51e18832cd507957a589e89452bd98164b3 (Multiple simultaneous
connections for clients)
* N_CONSENSUS_BOOTSTRAP_SOURCES concerns me. What if we think
(someday) that we should try three fallbacks and an authority? Or that we
should try an authority only after three fallbacks have failed? How much
code would we need to discard?
(sleeping time)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4483#comment:41>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list