[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #5506 [Tor Client]: Do we just keep downloading a consensus if our clock is wrong?

#5506: Do we just keep downloading a consensus if our clock is wrong?
------------------------+---------------------------------------------------
 Reporter:  arma        |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  normal      |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor Client  |        Version:                    
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------

Comment(by arma):

 I'm not actually sure what we should *do* in these cases. We don't want to
 just quit fetching, because then a jerk can give us a wrong consensus and
 we'll freeze in place. Some sort of "if the one we just got is the same as
 the one we already had, stop resetting time_to_download_next_consensus[i]"
 logic might be a good start. Another approach might be to reset
 time_to_download_next_consensus[i] if !c but be more lenient if the one we
 have is merely wrong. (Wrong like the consensus is from the future, I mean
 -- if the consensus is expired we need another one rsn.)

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