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

[Tor Bug Tracker & Wiki]

#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 isis):

 I read through some of the settings in the running instance of BridgeDB's
 bridgedb.conf file. There it specifies:

 {{{
 $ cat bridgedb.conf | grep descriptors
 # Files from which we read bridge descriptors, on start and on SIGHUP.
 BRIDGE_FILES = [ "../from-authority/bridge-descriptors" ]
 }}}

 and in Main.py, in the global CONFIG variable which is used for testing,
 these are:
 {{{
 lib/bridgedb/Main.py:    BRIDGE_FILES = [ "./cached-descriptors",
 "./cached-descriptors.new" ],
 }}}

 In the from-authority directory I found all three of these files, all with
 recent modification times, and the running BridgeDB process was not called
 with the '--testing' option, so it should only be reading the 'bridge-
 descriptors' file.

 I'm fairly sure that if I change BRIDGE_FILES in the running instance's
 config to {{{["./cached-descriptors", "./cached-descriptors.new"]}}} that
 it'll fix this, but I am nervous to change things without someone else who
 knows BridgeDB really well being available to help (I don't know how
 maintenance and deployments are done yet).

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