[tor-bugs] #9264 [BridgeDB]: Problem with transport lines in BridgeDB's bridge pool assignment files

[Tor Bug Tracker & Wiki]

#9264: Problem with transport lines in BridgeDB's bridge pool assignment files
--------------------------+----------------------------
     Reporter:  karsten   |      Owner:  isis
         Type:  defect    |     Status:  closed
     Priority:  major     |  Milestone:
    Component:  BridgeDB  |    Version:
   Resolution:  fixed     |   Keywords:  bridgedb-0.1.3
Actual Points:            |  Parent ID:
       Points:            |
--------------------------+----------------------------
Changes (by isis):

 * keywords:   => bridgedb-0.1.3
 * status:  needs_revision => closed
 * resolution:   => fixed


Comment:

 I merged sysrqb's `bug9264_rebased_1` branch into `develop` for version
 0.1.3. The bug where the distributors didn't have bridges in their
 hashrings was caused by a commit to make fingerprint string capitalisation
 consistent; I reverted it.

 I also merged the `hotfix/9264-descdigest-none` branch, which fixes a
 problem where, if the nickname was not to spec (longer than 19
 characters), then the nickname and descriptor digest are both set to
 `None` and `bridgedb.Bridges.parseStatusFile()` attempts to format the
 null descriptor digest into hexadecimal.

 @sysrqb: Thanks!

 @karsten: let me know if this does/does't fix the assignments.log files!

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