#2681: brainstorm ways to let Tor clients use yesterday's consensus more safely
-----------------------------------------------------+----------------------
Reporter: arma | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Tor:
0.2.4.x-final
Component: Tor Client | Version:
Keywords: dirauth-dos-resistance, proposal-needed | Parent: #2664
Points: | Actualpoints:
-----------------------------------------------------+----------------------
Changes (by mikeperry):
* keywords: => dirauth-dos-resistance, proposal-needed
* milestone: Tor: unspecified => Tor: 0.2.4.x-final
Comment:
With each new dirauth we add into the kool kids klub, it becomes less
likely we'll be able to contact at least half of them within 25 hours in
the event of something like the crash in the #2664 description.
What's the simplest thing we can get done on the 0.2.4.x timescale to
improve this situation? Can we just bump the consensus and descriptor
freshness limits?
In terms of what limit to bump to: I think we need to be able to survive
at least a 3 day weekend. If someone were to bring down the dirauths on
xmas, thanksgiving, or NYE, we need to not lose the Tor network because a
patch couldn't be written in time.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2681#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
