[tor-bugs] #572 [Tor Client]: fallback-consensus file impractical to use

[Tor Bug Tracker & Wiki]

#572: fallback-consensus file impractical to use
--------------------------------------------------+-------------------------
 Reporter:  arma                                  |           Type:  enhancement
   Status:  needs_review                          |       Priority:  major      
Milestone:  Tor: 0.2.4.x-final                    |      Component:  Tor Client 
  Version:  0.2.0.9-alpha                         |     Resolution:  None       
 Keywords:  performance bootstrap dos-resistance  |         Parent:  #2664      
   Points:                                        |   Actualpoints:             
--------------------------------------------------+-------------------------

Comment(by mikeperry):

 Ok, I reviewed this, but a couple more comments/questions:

 1. Making the dirauths also fallback dir mirrors might complicate with how
 we want to handle #4483. I think we want to be able to say "attempt to get
 the consensus from D dirauths and M fallback mirrors" somehow. See comment
 5 there for details. It looks like we can still the inspect dir_server_t
 is_authority flag to get this done, but that might be a reason for keeping
 them in fully disjoint lists instead? Or maybe not, since it's not the
 common case...
 2. Can you add an example fallback dirserver line in the comments for
 add_default_fallback_dir_servers()? It looks like a subset of the dirauth
 line syntax is acceptable, but an example would be great.

 Note: I don't know enough about directory activity to properly evaluate
 the correct use of the fallback dir servers vs dirauths in all cases, so
 perhaps my review doesn't count as exhaustive. But I can also test both
 this and #4483 with some firewall rules to block access to all of the
 dirauths once both are ready.

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