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

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#2895: BridgeDB assumes that cached-descriptors[.new] are in chronological order
----------------------+-----------------------------------------------------
 Reporter:  karsten   |          Owner:     
     Type:  defect    |         Status:  new
 Priority:  minor     |      Milestone:     
Component:  BridgeDB  |        Version:     
 Keywords:            |         Parent:     
   Points:            |   Actualpoints:     
----------------------+-----------------------------------------------------
 When parsing bridge descriptors, BridgeDB assumes that descriptors in the
 bridge descriptor files are in chronological order and that descriptors in
 cached-descriptors.new are newer than those in cached-descriptors.  If
 this is not the case, BridgeDB overwrites a bridge's IP address and OR
 port with those from an older descriptor.

 I think that the current cached-descriptors* files that Tor produces
 always have descriptors in chronological order.  But once we change that,
 e.g., when trying to limit the number of descriptors that Tor memorizes,
 BridgeDB will behave funny.

 We should look at the bridge descriptor that is referenced from the bridge
 network status by its publication time and ignore all other bridge
 descriptors from the same bridge.

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