[tor-bugs] #4011 [Tor Relay]: 0.2.3.3 relay won't fetch microdesc consensus on startup if it already has a normal consensus

[Tor Bug Tracker & Wiki]

#4011: 0.2.3.3 relay won't fetch microdesc consensus on startup if it already has
a normal consensus
-----------------------+----------------------------------------------------
 Reporter:  arma       |          Owner:                    
     Type:  defect     |         Status:  needs_review      
 Priority:  major      |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Relay  |        Version:  Tor: 0.2.3.3-alpha
 Keywords:             |         Parent:                    
   Points:             |   Actualpoints:                    
-----------------------+----------------------------------------------------

Comment(by arma):

 Patch looks fine to me. Yay.

 That said, deciding we need a new consensus if "c->valid_after > now"
 freaks me out. That isn't new behavior from this patch (so it should not
 stop the patch from being merged). But is it wise behavior? If my clock is
 set 5 hours in the past and I get a consensus that's not valid yet, do I
 just keep fetching a new one? I guess the same question holds for if my
 clock is 5 hours in the future and I keeping getting consensuses that are
 no longer valid. Is this a solved issue (e.g. somewhere we notice that the
 new copy is the same as the one we already have), or is this worth opening
 a separate ticket about?

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