Re: [tor-bugs] #8766 [Tor]: Tor never recovers when started with skewed clock

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#8766: Tor never recovers when started with skewed clock
------------------------+--------------------------------
     Reporter:  proper  |      Owner:
         Type:  defect  |     Status:  needs_review
     Priority:  normal  |  Milestone:  Tor: 0.2.7.x-final
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-client
Actual Points:          |  Parent ID:
       Points:          |
------------------------+--------------------------------
Changes (by arma):

 * status:  new => needs_review
 * milestone:  Tor: 0.2.??? => Tor: 0.2.7.x-final


Comment:

 Replying to [comment:5 arma]:
 > (What would happen if we just zeroed all the time_to_foo's on clock
 jump?)

 My ticket8766 branch does this, and it works -- you can start your Tor a
 week in the future, then fix the clock, and it will pretty speedily catch
 up and finish bootstrapping.

 There are still plenty of components of Tor that haven't been fixed here
 though -- the addressmaps come to mind, some of the cell timer statistics,
 maybe the circuit and channel lifetime checks, maybe the relay bandwidth
 and geoip histories, the time_to_download_next_consensus[] as mentioned
 above, a hidden service's next_upload_time, are probably all worth
 exploring too. And god only knows what happens to libevent event timers
 when the clock goes back a week.

 But all of this said, for the "Tails or Whonix first start" use case,
 maybe few of those matter in practice. I think this patch as-is helps in
 some cases and doesn't hurt in any.

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