[tor-bugs] #15866 [BridgeDB]: BridgeDB has less bridges because the BridgeAuthority appears to be giving it incorrect networkstatuses

Tor Bug Tracker & Wiki blackhole at torproject.org
Fri May 1 08:45:01 UTC 2015


#15866: BridgeDB has less bridges because the BridgeAuthority appears to be giving
it incorrect networkstatuses
-------------------------+-------------------------------------------------
     Reporter:  isis     |      Owner:  isis
         Type:  defect   |     Status:  closed
     Priority:           |  Milestone:
  critical               |    Version:
    Component:           |   Keywords:  bridgedb-parsers, bridgedb-dist,
  BridgeDB               |  bridgeauth, tor-auth, bridgedb-0.3.2
   Resolution:  fixed    |  Parent ID:
Actual Points:           |
       Points:           |
-------------------------+-------------------------------------------------

Comment (by isis):

 This worked quite well, with one minor glitch:

 From BridgeDB's log files:
 {{{
 07:32:28 INFO     L200:Main.load()              Done inserting 4643
 bridges into splitter.
 07:32:28 DEBUG    L204:persistent.save()        Saving state to:
 '/srv/bridges.torproject.org/run/bridgedb.state'
 07:32:28 DEBUG    L166:persistent.load()        Retrieving state from:
 '/srv/bridges.torproject.org/run/bridgedb.state'
 07:32:28 INFO     L428:Main.reload()            Bridges loaded: 3444
 }}}

 […]

 {{{
 07:32:29 INFO     L670:Bridges.addRing()        Bridges inserted into
 Email-IP4 subring: 990
 07:32:29 INFO     L670:Bridges.addRing()        Bridges inserted into
 Email-IP6 subring: 50
 07:32:29 INFO     L438:Main.reload()            Bridges allotted for Email
 distribution: 990
 }}}

 […]

 {{{
 07:32:30 INFO     L447:Main.reload()            Bridges allotted for HTTPS
 distribution: 2054
 07:32:30 INFO     L448:Main.reload()                    Num bridges:
 Filter set:
 07:32:30 INFO     L456:Main.reload()                    64 bridges
 filterAssignBridgesToRing filterBridgesByIP6
 07:32:30 INFO     L456:Main.reload()                    1052 bridges
 filterAssignBridgesToRing filterBridgesByIP4
 07:32:30 INFO     L456:Main.reload()                    45 bridges
 filterAssignBridgesToRing filterBridgesByIP6
 07:32:30 INFO     L456:Main.reload()                    1002 bridges
 filterAssignBridgesToRing
 07:32:30 INFO     L456:Main.reload()                    1002 bridges
 filterAssignBridgesToRing filterBridgesByIP4
 07:32:30 INFO     L456:Main.reload()                    1052 bridges
 filterAssignBridgesToRing
 07:32:30 INFO     L459:Main.reload()            Total subrings for HTTPS:
 6
 }}}

 It's ''probably'' just an issue with one of the old hashring classes in
 `bridgedb.Bridges` having a stupid/buggy `__len__()` method that double-
 counts bridges which are in a hashring and also in one of that hashring's
 sub-hashrings.

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


More information about the tor-bugs mailing list