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

Tor Bug Tracker & Wiki blackhole at torproject.org
Tue Aug 13 11:21:16 UTC 2013


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

  * status:  reopened => needs_information


Comment:

 Replying to [comment:20 asn]:
 > I'm not sure if this should be closed. We still don't know why there
 were duplicate bridges in that `self.bridges` list. There must be some
 weirdness somewhere -- we should either fix it, or document it.

 We should definitely fix it...unless it is "impossible".

 > I'll reopen this ticket till we do some more digging on what sysrqb's
 branch hotfixed. Otherwise, we will never get to it.
 Yup. We can also open a new ticket for "why does ponticum import duplicate
 bridges", but the history here may help, but the Summary isn't exactly
 truthful anymore.

 Basically, we knew BridgeDB was importing a single bridge multiple times
 when it parsed the descriptors. This hotfix simply checks if the bridge we
 just parsed was already imported and skips it if we already know about it,
 thus preventing duplicates.

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


More information about the tor-bugs mailing list