[tor-bugs] #16943 [Tor]: Implement prop250 (Random Number Generation During Tor Voting)

Tor Bug Tracker & Wiki blackhole at torproject.org
Fri Sep 4 12:11:47 UTC 2015


#16943: Implement prop250 (Random Number Generation During Tor Voting)
------------------------+--------------------------
     Reporter:  asn     |      Owner:
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:  Tor: 0.2.???
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-hs
Actual Points:          |  Parent ID:  #8244
       Points:          |
------------------------+--------------------------

Comment (by asn):

 So we David we discussed a possible refactoring here that would allow us
 to introduce SR doc logic to functions like
 `networkstatus_add_detached_signatures()`.

 The idea is that we will make a new data structure called `consensus_t`
 which will be used in places where we don't care about the specific
 consensus flavor. This data structure will be able to contain
 `networkstatus_t` or `shared_random_doc_t` or any other weird flavor we
 come up in the future.

 Then we can have some methods for `consensus_t`, which based on the flavor
 returns you the appropriate data structure.

 Then we will need to refactor all the functions mentioned in the previous
 comment (and a few more), to be able to do their thing on a
 `networkstatus_t` but then also do a similar thing for
 `shared_random_doc_t`. This will require lots of hairy code to be
 refactored which is scary, but doable.

 Any opinions on this strategy?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16943#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list