[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #10542 [Tor]: Bug: Generated a networkstatus consensus we couldn't parse.
#10542: Bug: Generated a networkstatus consensus we couldn't parse.
------------------------+--------------------------------
Reporter: arma | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.5.x-final
Component: Tor | Version:
Resolution: | Keywords: tor-auth
Actual Points: | Parent ID:
Points: |
------------------------+--------------------------------
Changes (by karsten):
* cc: ln5, Sebastian (added)
Comment:
What did moria1 say five minutes earlier when it generated its vote, when
it uploaded it to the other authorities, and 2:30 minutes earlier when the
other authorities asked for its vote? Can you post the logs from that
time, too?
What did the other authorities say? Can somebody please post notice-level
logs of that time?
Agreed about the two bugs, though they seem to only affect moria1's own
internal logging, not the voting process: nobody accepted moria1's vote
nor included it in the consensus. (At least there are no votes from
moria1 in the metrics archives between 2014-01-02 10:00 UTC to 2014-01-03
00:00 UTC, and the consensuses from that time contain neither moria1's
`dir-source` line nor `directory-signature`.) That's good. I wonder if
we should specify this any further in dir-spec.txt than:
{{{
Authorities MUST generate a new signing key and corresponding
certificate before the key expires.
}}}
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10542#comment:1>
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