#2878: Don't bootstrap from an old consensus if we're about to replace it -------------------------------------------------+------------------------- Reporter: Sebastian | Owner: (none) Type: enhancement | Status: new Priority: High | Milestone: Tor: | unspecified Component: Core Tor/Tor | Version: Severity: Major | Resolution: Keywords: performance, bootstrap, tor-client, | Actual Points: s8-performance, s8-errors, 040-roadmap- | proposed | Parent ID: #23605 | Points: Reviewer: | Sponsor: | Sponsor8-can -------------------------------------------------+-------------------------
Comment (by nickm): It's possible we don't actually want to do this. This ticket is older than microdescriptors, older than the onion key rotation changes of prop#274 (see #21641) and (I think) older than the live/reasonably live distinction. Most of the microdescriptors from any reasonably live consensus should still be usable these days, especially The worst case here is when we have a consensus but we shut down before we can fetch any microdescriptors for it, and we start up again in the last minutes when the consensus is still reasonably live. I think even then the damage should be limited. Taylor nodes that some other issues discussed above are variants on the jump-to-80% problem (see #22266). I say that we should either wontfix, or mark this as needs_information, said information being "what is the measurable effect of this issue in practice?" -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2878#comment:21> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs