[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):
Hmmmm. The sentence that reads...
"Each consensus method specifies an order in which these items MUST occur"
... strikes me as the same as what we previously had...
"The preamble contains the following items. They MUST occur in the order
given here:"
When I read 'each consensus method specifies an order' I think 'ok, so
this is the order'. My change (simply changing MUST to SHOULD) drops any
strong assurance that what follows is the actual ordering.
That said, I don't care too strongly about this. This patch feels like a
lateral move to me. If Nick prefers it I don't have a strong objection to
merging it.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21059#comment:25>
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