[tor-bugs] #19124 [Core Tor/Tor]: Shared Random and Half-Hour Consensuses

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#19124: Shared Random and Half-Hour Consensuses
------------------------------+--------------------------------
     Reporter:  teor          |      Owner:
         Type:  defect        |     Status:  new
     Priority:  Medium        |  Milestone:  Tor: 0.2.9.x-final
    Component:  Core Tor/Tor  |    Version:
     Severity:  Normal        |   Keywords:
Actual Points:                |  Parent ID:  #16943
       Points:                |   Reviewer:
      Sponsor:                |
------------------------------+--------------------------------
 My test authority was asleep for an hour, and so it didn't have a recent
 consensus. It started voting at 10:30 for round commit 3/reveal 3, but the
 rest of the network wasn't voting for commit 3/reveal 3 until 11.

 How does an authority recover from this situation if it has thrown away
 its state at 1030?

 Do we fix this by implemeting #19045 (keep voting for shared random
 values)?
 Or does that make this worse?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19124>
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