[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: closed
Priority: High | Milestone: Tor: 0.3.0.x-final
Component: Core Tor/Tor | Version:
Severity: Major | Resolution: fixed
Keywords: | Actual Points:
Parent ID: | Points: 0.1
Reviewer: | Sponsor:
--------------------------+------------------------------------
Changes (by asn):
* status: reopened => closed
* resolution: => fixed
Comment:
Replying to [comment:31 atagar]:
> Hi George. Actually, my change from comment:20 was already pushed
(though by changing it back to MUST this reverted it). How in particular
are you inclined toward combining these changes?
>
> comment:24 has the reason I'm leaning toward making this SHOULD.
However, if you'd care to do an audit that the spec's order is now
accurate and ensure we're really careful not to keep making mistakes on
this we can go ahead and make it a MUST clause.
Hey Damian,
sorry about that. I reverted my commit, and now strict ordering is
`SHOULD`.
I'm closing this ticket again, given that we didn't hear from teor. I'm
personally OK with the current state of the spec.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21059#comment:32>
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