[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:              
     Type:  defect    |         Status:  needs_review
 Priority:  major     |      Milestone:              
Component:  BridgeDB  |        Version:              
 Keywords:            |         Parent:              
   Points:            |   Actualpoints:              
----------------------+-----------------------------------------------------

Comment(by aagbsn):

 BridgeDB was incorrectly using only the new (cached-extrainfo.new)
 descriptors.
 I have reverted to using the cached-extrainfo file, but as noted above we
 don't learn about the extra-info (and pluggable transports) till 2hrs
 later. sysrqb's fix looks like it should address this (thanks!).

 From Karsten's response in the email thread, clarifying extrainfo
 behavior:

 {{{
 No.  Tonga writes descriptors to cached-extrainfo roughly every two
 hours.  It then writes incoming descriptors to cached-extrainfo.new
 without touching cached-extrainfo.  Only two hours later, it rewrites
 cached-extrainfo and puts all descriptors in it that are still valid.
 It also deletes cached-extrainfo.new.
 }}}

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