[tor-bugs] #24661 [Core Tor/Tor]: accept a reasonably live consensus for guard selection

[Tor Bug Tracker & Wiki]

#24661: accept a reasonably live consensus for guard selection
-------------------------------------------------+-------------------------
 Reporter:  catalyst                             |          Owner:  teor
     Type:  defect                               |         Status:
                                                 |  assigned
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  0.3.6.x-final
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  0.3.0.1-alpha
 Severity:  Normal                               |     Resolution:
 Keywords:  bootstrap, clock-skew,               |  Actual Points:
  s8-bootstrap, s8-errors, ux,                   |
  033-triage-20180320, 034-roadmap-proposed,     |
  034-triage-20180328, 034-included-20180328,    |
  034-deferred-20180602, 035-removed-20180711    |
Parent ID:  #23605                               |         Points:  1
 Reviewer:                                       |        Sponsor:
                                                 |  Sponsor8-can
-------------------------------------------------+-------------------------
Changes (by teor):

 * owner:  catalyst => teor
 * version:   => Tor: 0.3.0.1-alpha
 * milestone:  Tor: unspecified => Tor: 0.3.6.x-final


Comment:

 I have a draft branch for this bug.

 I still need to fix the entry nodes unit tests.

 There also seem to be other parts of tor's codebase that require a recent
 consensus:
 {{{
 Nov 05 15:29:04.000 [notice] Bootstrapped 25%: Loading networkstatus
 consensus
 Nov 05 15:29:51.000 [notice] I learned some more directory information,
 but not enough to build a circuit: We have no usable consensus.
 Nov 05 15:29:52.000 [notice] Bootstrapped 40%: Loading authority key certs
 Nov 05 15:29:55.000 [warn] Our clock is 30 minutes, 6 seconds behind the
 time published in the consensus network status document (2018-11-05
 06:00:00 UTC).  Tor needs an accurate clock to work correctly. Please
 check your time and date settings!
 Nov 05 15:29:55.000 [warn] Received microdesc flavor consensus with skewed
 time (CONSENSUS): It seems that our clock is behind by 30 minutes, 6
 seconds, or that theirs is ahead. Tor requires an accurate clock to work:
 please check your time, timezone, and date settings.
 Nov 05 15:29:55.000 [warn] Problem bootstrapping. Stuck at 40%: Loading
 authority key certs. (Clock skew -1806 in microdesc flavor consensus from
 CONSENSUS; CLOCK_SKEW; count 1; recommendation warn; host ? at ?)
 Nov 05 15:29:55.000 [notice] I learned some more directory information,
 but not enough to build a circuit: We have no recent usable consensus.
 Nov 05 15:29:55.000 [notice] I learned some more directory information,
 but not enough to build a circuit: We have no recent usable consensus.
 Nov 05 17:27:43.000 [notice] Your system clock just jumped 7056 seconds
 forward; assuming established circuits no longer work.
 }}}

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