Re: [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:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.1-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  bootstrap, clock-skew, ux, 035   |  Actual Points:
  -backport-maybe, 034-backport-maybe-not, 033   |
  -backport-maybe-not, 033-triage-20180320, 034  |
  -roadmap-proposed, 034-triage-20180328,|
  034-included-20180328, 034-deferred-20180602,  |
  035-removed-20180711   |
Parent ID:  #28018   | Points:  1
 Reviewer:  catalyst |Sponsor:
-+-
Changes (by asn):

 * status:  merge_ready => closed
 * resolution:   => fixed


Comment:

 Backported to maint-0.3.5 and release-0.3.5.

 
https://gitweb.torproject.org/tor.git/commit/?h=maint-0.3.5=9bfe4ed6dd666bb276e35b6e5c8c3de0c218bce0

 https://gitweb.torproject.org/tor.git/commit/?h=release-0.3.5

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  bootstrap, clock-skew, ux, 035   |  Actual Points:
  -backport-maybe, 034-backport-maybe-not, 033   |
  -backport-maybe-not, 033-triage-20180320, 034  |
  -roadmap-proposed, 034-triage-20180328,|
  034-included-20180328, 034-deferred-20180602,  |
  035-removed-20180711   |
Parent ID:  #28018   | Points:  1
 Reviewer:  catalyst |Sponsor:
-+-
Changes (by hefee):

 * cc: torproject@… (added)


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  bootstrap, clock-skew, ux, 035   |  Actual Points:
  -backport-maybe, 034-backport-maybe-not, 033   |
  -backport-maybe-not, 033-triage-20180320, 034  |
  -roadmap-proposed, 034-triage-20180328,|
  034-included-20180328, 034-deferred-20180602,  |
  035-removed-20180711   |
Parent ID:  #28018   | Points:  1
 Reviewer:  catalyst |Sponsor:
-+-
Changes (by gaba):

 * keywords:
 bootstrap, clock-skew, s8-bootstrap, s8-errors, ux, 035-backport-
 maybe, 034-backport-maybe-not, 033-backport-maybe-not,
 033-triage-20180320, 034-roadmap-proposed, 034-triage-20180328,
 034-included-20180328, 034-deferred-20180602, 035-removed-20180711
 =>
 bootstrap, clock-skew, ux, 035-backport-maybe, 034-backport-maybe-not,
 033-backport-maybe-not, 033-triage-20180320, 034-roadmap-proposed,
 034-triage-20180328, 034-included-20180328, 034-deferred-20180602,
 035-removed-20180711
 * sponsor:  Sponsor8-can =>


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.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, 035-backport- |
  maybe, 034-backport-maybe-not, 033-backport-   |
  maybe-not, 033-triage-20180320, 034-roadmap-   |
  proposed, 034-triage-20180328, |
  034-included-20180328, 034-deferred-20180602,  |
  035-removed-20180711   |
Parent ID:  #28018   | Points:  1
 Reviewer:  catalyst |Sponsor:
 |  Sponsor8-can
-+-

Comment (by teor):

 Replying to [comment:21 nickm]:
 > Merged  PR 536 to 0.4.0; marking for possible backport to 0.3.5.
 >
 > (Do we still think this is backport material?)

 I think this change is simple enough to backport. And it would be nice to
 have in LTS.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.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, 035-backport- |
  maybe, 034-backport-maybe-not, 033-backport-   |
  maybe-not, 033-triage-20180320, 034-roadmap-   |
  proposed, 034-triage-20180328, |
  034-included-20180328, 034-deferred-20180602,  |
  035-removed-20180711   |
Parent ID:  #23605   | Points:  1
 Reviewer:  catalyst |Sponsor:
 |  Sponsor8-can
-+-

Comment (by teor):

 It would be nice to have the next LTS work with a skewed clock.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.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, 035-backport- |
  maybe, 034-backport-maybe-not, 033-backport-   |
  maybe-not, 033-triage-20180320, 034-roadmap-   |
  proposed, 034-triage-20180328, |
  034-included-20180328, 034-deferred-20180602,  |
  035-removed-20180711   |
Parent ID:  #23605   | Points:  1
 Reviewer:  catalyst |Sponsor:
 |  Sponsor8-can
-+-

Comment (by nickm):

 Merged  PR 536 to 0.4.0; marking for possible backport to 0.3.5.

 (Do we still think this is backport material?)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.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, 035-backport- |
  maybe, 034-backport-maybe-not, 033-backport-   |
  maybe-not, 033-triage-20180320, 034-roadmap-   |
  proposed, 034-triage-20180328, |
  034-included-20180328, 034-deferred-20180602,  |
  035-removed-20180711   |
Parent ID:  #23605   | Points:  1
 Reviewer:  catalyst |Sponsor:
 |  Sponsor8-can
-+-
Changes (by nickm):

 * milestone:  Tor: 0.4.0.x-final => Tor: 0.3.5.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.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, 035-backport- |
  maybe, 034-backport-maybe-not, 033-backport-   |
  maybe-not, 033-triage-20180320, 034-roadmap-   |
  proposed, 034-triage-20180328, |
  034-included-20180328, 034-deferred-20180602,  |
  035-removed-20180711   |
Parent ID:  #23605   | Points:  1
 Reviewer:  catalyst |Sponsor:
 |  Sponsor8-can
-+-
Changes (by catalyst):

 * status:  needs_review => merge_ready


Comment:

 Thanks! Patch looks good to me.

 I verified the fix using libfaketime and manual testing.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.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, 035-backport- |
  maybe, 034-backport-maybe-not, 033-backport-   |
  maybe-not, 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
-+-

Comment (by teor):

 When I set my clock 12 hours behind, I see this error with maint-0.3.5 and
 my branch:
 {{{
 $ src/app/tor
 Nov 23 05:07:03.296 [notice] Tor 0.3.5.5-alpha-dev (git-a9820f072bf1bd79)
 running on Darwin with Libevent 2.1.8-stable, OpenSSL 1.0.2p, Zlib 1.2.11,
 Liblzma 5.2.4, and Libzstd 1.3.7.
 ...
 Nov 23 05:07:03.000 [notice] Bootstrapped 0%: Starting
 Nov 23 05:07:03.000 [notice] Starting with guard context "default"
 Nov 23 05:07:04.000 [notice] Bootstrapped 5%: Connecting to directory
 server
 Nov 23 05:07:05.000 [notice] Bootstrapped 10%: Finishing handshake with
 directory server
 Nov 23 05:07:06.000 [notice] Bootstrapped 15%: Establishing an encrypted
 directory connection
 Nov 23 05:07:06.000 [notice] Bootstrapped 20%: Asking for networkstatus
 consensus
 Nov 23 05:07:06.000 [notice] Bootstrapped 25%: Loading networkstatus
 consensus
 Nov 23 05:07:10.000 [notice] I learned some more directory information,
 but not enough to build a circuit: We have no usable consensus.
 Nov 23 05:07:10.000 [notice] Bootstrapped 40%: Loading authority key certs
 Nov 23 05:07:12.000 [warn] Our clock is 10 hours, 52 minutes behind the
 time published in the consensus network status document (2018-11-23
 06:00:00 UTC).  Tor needs an accurate clock to work correctly. Please
 check your time and date settings!
 Nov 23 05:07:12.000 [warn] Received microdesc flavor consensus with skewed
 time (CONSENSUS): It seems that our clock is behind by 10 hours, 52
 minutes, or that theirs is ahead. Tor requires an accurate clock to work:
 please check your time, timezone, and date settings.
 Nov 23 05:07:12.000 [warn] Problem bootstrapping. Stuck at 40%: Loading
 authority key certs. (Clock skew -39169 in microdesc flavor consensus from
 CONSENSUS; CLOCK_SKEW; count 1; recommendation warn; host ? at ?)
 }}}

 When I set my clock 12 hours ahead, on maint-0.3.5 I see:
 {{{
 $ src/app/tor
 Nov 24 05:09:33.482 [notice] Tor 0.3.5.5-alpha-dev (git-a9820f072bf1bd79)
 running on Darwin with Libevent 2.1.8-stable, OpenSSL 1.0.2p, Zlib 1.2.11,
 Liblzma 5.2.4, and Libzstd 1.3.7.
 ...
 Nov 24 05:09:33.000 [notice] Bootstrapped 0%: Starting
 Nov 24 05:09:33.000 [notice] Starting with guard context "default"
 Nov 24 05:09:34.000 [notice] Bootstrapped 5%: Connecting to directory
 server
 Nov 24 05:09:35.000 [notice] Bootstrapped 10%: Finishing handshake with
 directory server
 Nov 24 05:09:36.000 [notice] Bootstrapped 15%: Establishing an encrypted
 directory connection
 Nov 24 05:09:36.000 [notice] Bootstrapped 20%: Asking for networkstatus
 consensus
 Nov 24 05:09:37.000 [notice] Bootstrapped 25%: Loading networkstatus
 consensus
 Nov 24 05:09:41.000 [notice] I learned some more directory information,
 but not enough to build a circuit: We have no usable consensus.
 Nov 24 05:09:42.000 [notice] Bootstrapped 40%: Loading authority key certs
 Nov 24 05:09:44.000 [notice] The current consensus has no exit nodes. Tor
 can only build internal paths, such as paths to onion services.
 Nov 24 05:09:44.000 [notice] Bootstrapped 45%: Asking for relay
 descriptors for internal paths
 Nov 24 05:09:44.000 [notice] I learned some more directory information,
 but not enough to build a circuit: We need more microdescriptors: we have
 0/6279, and can only build 0% of likely paths. (We have 0% of guards bw,
 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) =
 0% of path bw.)
 ...
 Nov 24 05:09:49.000 [notice] Bootstrapped 50%: Loading relay descriptors
 for internal paths
 Nov 24 05:09:51.000 [notice] The current consensus contains exit nodes.
 Tor can build exit and internal paths.
 Nov 24 05:09:53.000 

Re: [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:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.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, 035-backport- |
  maybe, 034-backport-maybe-not, 033-backport-   |
  maybe-not, 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
-+-

Comment (by teor):

 The appveyor tests fail due to #28574.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.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, 035-backport- |
  maybe, 034-backport-maybe-not, 033-backport-   |
  maybe-not, 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):

 * keywords:
 bootstrap, clock-skew, s8-bootstrap, s8-errors, ux,
 033-triage-20180320, 034-roadmap-proposed, 034-triage-20180328,
 034-included-20180328, 034-deferred-20180602, 035-removed-20180711
 =>
 bootstrap, clock-skew, s8-bootstrap, s8-errors, ux, 035-backport-
 maybe, 034-backport-maybe-not, 033-backport-maybe-not,
 033-triage-20180320, 034-roadmap-proposed, 034-triage-20180328,
 034-included-20180328, 034-deferred-20180602, 035-removed-20180711
 * status:  needs_revision => needs_review


Comment:

 This code had non-trivial merge conflicts when cherry-picked to 0.3.3 or
 0.3.4, so I just made an 0.3.5 branch.

 See my pull request:
 https://github.com/torproject/tor/pull/536

 I am still testing it with clock skew.
 I'd like to be able to reproduce clock skew tests, maybe I can work out
 how to do that with chutney.

 The stem test will fail due to #28571.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.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):

 * cc: catalyst (added)
 * status:  assigned => needs_revision


Comment:

 Here's my draft pull request:
 https://github.com/torproject/tor/pull/532

 The test_outdated_dirserver_exclusion unit tests fail, and I can't work
 out why.
 `make test-network-all` passes, but I still need to test with clock skew.

 The stem integ tests will fail due to #28550.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  catalyst
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 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
-+-

Comment (by nickm):

 I think that it is fine to make this change.  It's normal for clients to
 use guards that are chosen based on past consensuses.

 It might be good to make sure that we have at least tried to fetch a live
 consensus before we do this, though.  Maybe we should have the test be
 "have_reasonably_live_consensus() ||
 have_received_a_consensus_in_the_last_N_hours()"?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  catalyst
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 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 catalyst):

 * points:   => 1
 * parent:   => #23605


Comment:

 Reparent. The actual work to accomplish this is probably fairly small. The
 hard part is deciding whether it introduces too much risk.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  catalyst
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 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:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by intrigeri):

 * cc: intrigeri (added)


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  catalyst
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  bootstrap, clock-skew,   |  Actual Points:
  s8-bootstrap, s8-errors, ux,   |
  033-triage-20180320, 034-roadmap-proposed  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by nickm):

 * milestone:  Tor: 0.3.3.x-final => Tor: 0.3.4.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  catalyst
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  bootstrap, clock-skew,   |  Actual Points:
  s8-bootstrap, s8-errors, ux,   |
  033-triage-20180320, 034-roadmap-proposed  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by dgoulet):

 * keywords:
 bootstrap, clock-skew, s8-bootstrap, s8-errors, ux,
 033-triage-20180320, 033-removed-20180320
 =>
 bootstrap, clock-skew, s8-bootstrap, s8-errors, ux,
 033-triage-20180320, 034-roadmap-proposed


Comment:

 This is sponsor 8 stuff. It should be a subtasks of a master tasks from
 our roadmap. Maybe 034 or 035, not sure but lets consider it for 034.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [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:
 |  catalyst
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  bootstrap, clock-skew,   |  Actual Points:
  s8-bootstrap, s8-errors, ux|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by asn):

 * cc: asn (added)


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[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:   |  Owner:  catalyst
  catalyst   |
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:  Tor: 0.3.3.x-final
Component:  Core |Version:
  Tor/Tor|   Keywords:  bootstrap, clock-skew,
 Severity:  Normal   |  s8-bootstrap, s8-errors, ux
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
  Sponsor8-can   |
-+-
 Clients with clocks skewed far enough in the future to never get a live
 consensus, but still have a reasonably live one, end up downloading
 descriptors and then getting stuck on guard selection.  This is a rather
 bad user experience because bootstrap progress appears to get stuck at 80%
 or 85% even though something rather fundamental (time of day) is wrong.

 It's not clear that a reasonably live consensus is dangerous to use for
 guard selection, so always accept a reasonably live consensus instead of a
 live one for guard selection.

 Ticket #2878 covers the case of deferring descriptor downloads if the
 consensus isn't live, which would also improve the UX but might not be
 necessary if we implement the solution in this ticket.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs