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

Re: [tor-bugs] #2895 [BridgeDB]: BridgeDB assumes that cached-descriptors[.new] are in chronological order

#2895: BridgeDB assumes that cached-descriptors[.new] are in chronological order
--------------------------+----------------------------------------------
     Reporter:  karsten   |      Owner:  isis
         Type:  defect    |     Status:  closed
     Priority:  minor     |  Milestone:
    Component:  BridgeDB  |    Version:
   Resolution:  fixed     |   Keywords:  bridgedb-parsers, bridgedb-0.3.0
Actual Points:            |  Parent ID:
       Points:            |
--------------------------+----------------------------------------------

Comment (by arma):

 Replying to [comment:3 isis]:
 > to my knowledge, BridgeDB has never had `cached-descriptor*` files

 Hm? That's how bridgedb used to know what bridges exist -- Tonga would
 export its cached-descriptor* files and bridgedb would import them.

 In fact, I'm a bit confused that it doesn't still have them, yet there are
 extrainfo descriptors. How do you know which extrainfo descriptor matches
 up to which bridge descriptor? Isn't that what the "extra-info-digest"
 line in the bridge descriptor is for?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2895#comment:4>
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