[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #21059 [Core Tor/Tor]: shared-rand-current-value violates spec
#21059: shared-rand-current-value violates spec
--------------------------+------------------------------------
Reporter: atagar | Owner: asn
Type: defect | Status: needs_review
Priority: High | Milestone: Tor: 0.3.0.x-final
Component: Core Tor/Tor | Version:
Severity: Major | Resolution:
Keywords: | Actual Points:
Parent ID: | Points: 0.1
Reviewer: | Sponsor:
--------------------------+------------------------------------
Comment (by atagar):
> We should say that anybody parsing a consensus or a vote MUST accept
them in any order, but that authorities building a consensus MUST produce
them in a specific order, and then we specify that specific order.
For what it's worth this doesn't change things for Stem. Without
validation Stem is quite happy with the consensus - it's just validation
squawking because... well, it's wrong.
Without these validation checks we wouldn't know about this issue at all,
so I'm inclined to day 'everything working as intended on the stem and
spec front'. We can fix this with a tor change that moves the property to
the right spot, and await that release.
Concerning DocTor, I can make a temporary tweak so it ignores this
particular issue until the fix is live.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21059#comment:7>
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