[tor-bugs] #20966 [Core Tor/Tor]: Parts of deployed shared random protocol are specified only in the proposal
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Dec 14 02:42:30 UTC 2016
#20966: Parts of deployed shared random protocol are specified only in the proposal
------------------------------+---------------------
Reporter: arma | Owner:
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Core Tor/Tor | Version:
Severity: Normal | Keywords: SponsoR
Actual Points: | Parent ID:
Points: | Reviewer:
Sponsor: |
------------------------------+---------------------
In dir-spec.txt, commit c4ae4dd31 gave us lines like
{{{
+ Denotes a directory authority commit for the shared randomness
+ protocol, containing the commitment value and potentially also
the
+ reveal value. See sections [COMMITREVEAL] and [VALIDATEVALUES] of
+ proposal 250 on how to generate and validate these values.
}}}
That's a great improvement over just leaving it implicit. But if we have a
goal of having Tor specified in the spec files (is that true?), then we
should migrate the key sections from the proposal file to either dir-spec
or a new srv-spec file.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20966>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list