[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

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

#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:
Actual Points:            |  Parent ID:
       Points:            |
--------------------------+-------------------------------

Comment (by karsten):

 Replying to [comment:22 sysrqb]:
 > So, next stop bridge auth.

 This is expected behavior by the bridge authority.  It simply sends you
 its local descriptor caches, and those may contain older descriptors.
 This isn't something to fix, it's supposed to be like that.

 Here's how you'd filter out the latest descriptors of currently running
 bridges:

  - Go through the bridge network status and note down descriptor digests
 of entries with the Running flag.
  - Go through server descriptors by descriptor digest and note down the
 extra-info digests of corresponding extra-info descriptors.
  - Go through extra-info descriptors by extra-info digest and learn the
 information you wanted to learn.

 Does BridgeDB already use stem?  This is something where stem would be
 pretty helpful.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9264#comment:23>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs