shared-rand-current-value violates spec
-
- View options
Closed (moved) created by
Damian Johnson
Hi Nick. Shared randomness just made it into the consensus and it's making Stem's validator squawk. Trouble is that it's in the wrong position in the header. According to the spec...
The preamble contains the following items. They MUST occur in the
order given here:However, shared-rand-current-value appears last...
% wget http://128.31.0.39:9131/tor/status-vote/current/consensus
% less consensus
...
required-client-protocols Cons=1-2 Desc=1-2 DirCache=1 HSDir=1 HSIntro=3 HSRend=1 Link=4 LinkAuth=1 Microdesc=1-2 Relay=2
required-relay-protocols Cons=1 Desc=1 DirCache=1 HSDir=1 HSIntro=3 HSRend=1 Link=3-4 LinkAuth=1 Microdesc=1 Relay=1-2
params CircuitPriorityHalflifeMsec=30000 NumDirectoryGuards=3 NumEntryGuards=1 NumNTorsPerTAP=100 Support022HiddenServices=0 UseNTorHandshake=1 UseOptimisticData=1 bwauthpid=1 cbttestfreq=60 pb_disablepct=0 usecreatefast=0
shared-rand-current-value 6 nwr/w2uC49g/ZxbGpshs0w2nqWWqCsrHWzQhkuelAgA=
dir-source dannenberg 0232AF901C31A04EE9848595AF9BB7620D4C5B2E dannenberg.torauth.de 193.23.244.244 80 443
contact Andreas Lehner
...Think I'll mark this as 'high' since it's a new regression in the live consensuses. Gonna hazard to guess we'll need to update the spec rather than tor since this has already made it into a release?
Kinda unfortunate since it means it won't live with the other shared randomness attributes...
Attributes
Assignees
Labels
Milestone
Dates
Start: None
Due: None
Time tracking
Spent
0h
Estimate
0h 48m