[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #25756 [Core Tor/Tor]: EARLY_CONSENSUS_NOTICE_SKEW of 60 is too strict for some drifting dirauth clocks
#25756: EARLY_CONSENSUS_NOTICE_SKEW of 60 is too strict for some drifting dirauth
clocks
-------------------------------------------------+-------------------------
Reporter: Dbryrtfbcbhgf | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone: Tor:
| unspecified
Component: Core Tor/Tor | Version: Tor:
| 0.3.2.10
Severity: Normal | Resolution:
Keywords: clock-skew, s8-errors, 034-roadmap- | Actual Points:
proposed |
Parent ID: | Points:
Reviewer: | Sponsor:
| Sponsor8-can
-------------------------------------------------+-------------------------
Changes (by catalyst):
* keywords: clock-skew, s8-errors => clock-skew, s8-errors, 034-roadmap-
proposed
Comment:
During this week's meeting, we decided it would be a good idea to relax
this test to account for the voting schedule. That way for a client or
relay to get a "consensus is coming from the future" warning, enough
dirauths would have to have their clocks skewed by about the same amount.
A single dirauth with an early clock shouldn't be able to induce this
warning by releasing a consensus early. (This is what happened with
dizum.)
arma says the `voting-delay` consensus parameter is something we want to
look at if we want to not hard code this.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25756#comment:14>
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