#26485: June mystery: the microdesc consensus is getting 9 sigs, but the ns
consensus is getting only 5
 Reporter:  arma                                 |          Owner:  nickm
     Type:  defect                               |         Status:
                                                 |  needs_review
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  0.3.5.x-final
Component:  Core Tor/Tor                         |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tor-dirauth, fast-fix, 035-triaged-  |  Actual Points:
  in-20180711 029-backport 032-backport          |
  033-backport 034-backport                      |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
Changes (by nickm):

 * keywords:  tor-dirauth, fast-fix, 035-triaged-in-20180711 =>
     tor-dirauth, fast-fix, 035-triaged-in-20180711 029-backport
     032-backport 033-backport 034-backport
 * status:  accepted => needs_review


 I've done a minimal version of this in `bug26485_029`, PR at

 All this does is:
   * warn the voters if any authority has voted for a version with a space
 in it
   * warn the authority operator if they configure an invalid-looking
 version list
   * when generating a vote, to split any versions that seem to have spaces
 in them

 I considered other changes as well, but I want to avoid changes that would
 affect the output of the consensus algorithm -- especially in a branch
 we're thinking of backporting to 0.2.9.

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26485#comment:20>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
tor-bugs mailing list

Reply via email to