[tor-bugs] #1300 [Tor Relay]: Authority that doesn't make a consensus never fetches one from elsewhere

Tor Bug Tracker & Wiki torproject-admin at torproject.org
Sun Sep 12 22:38:44 UTC 2010


#1300: Authority that doesn't make a consensus never fetches one from elsewhere
--------------------------------+-------------------------------------------
 Reporter:  arma                |         Type:  defect   
   Status:  needs_review        |     Priority:  normal   
Milestone:  Tor: 0.2.2.x-final  |    Component:  Tor Relay
  Version:  0.2.1.24            |   Resolution:  None     
 Keywords:  easy                |       Parent:           
--------------------------------+-------------------------------------------

Comment(by arma):

 Another way to say "we spent at least 1/4 of the next period giving out
 our old consensus" is "we spend at least half the period where relays are
 asking us for an updated consensus stubbornly giving out the old one".
 That's no good.

 If the "+ 15 minutes" thing is to handle clock skew, it's our own clock
 that's the only one that matters. We make the consensus, when we think we
 should. Nobody else is going to send us one.

 Seems to me that we should put authorities in the "extra early" schedule
 category:
 {{{
       /* Some clients may need the consensus sooner than others. */
       if (options->FetchDirInfoExtraEarly) {
         dl_interval = 60;
         if (min_sec_before_caching + dl_interval > interval)
           dl_interval = interval/2;
       }
 }}}

 That is, add a "and authdir_mode_v3()" clause to the if.

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


More information about the tor-bugs mailing list