Re: [tor-bugs] #32438 [Applications/Tor Launcher]: Inconsistent failure-then-success bootstrap behavior with clock set 24h in the past

[Tor Bug Tracker & Wiki]

#32438: Inconsistent failure-then-success bootstrap behavior with clock set 24h 
in
the past
-+-
 Reporter:  intrigeri|  Owner:  brade
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Launcher|Version:
 Severity:  Normal   | Resolution:
 Keywords:  bootstrap, clock-skew, usability,|  Actual Points:
  ux, s8-errors, AffectsTails|
Parent ID:  #23508   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by mcs):

 * status:  new => needs_information


Comment:

 Shouldn't this be a Core Tor ticket? Tor Launcher simply reports errors or
 accepts "success" as reported by Tor.

--
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] #32438 [Applications/Tor Launcher]: Inconsistent failure-then-success bootstrap behavior with clock set 24h in the past

[Tor Bug Tracker & Wiki]

#32438: Inconsistent failure-then-success bootstrap behavior with clock set 24h 
in
the past
-+-
 Reporter:  intrigeri|  Owner:  brade
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Launcher|Version:
 Severity:  Normal   | Resolution:
 Keywords:  bootstrap, clock-skew, usability,|  Actual Points:
  ux, s8-errors, AffectsTails|
Parent ID:  #23508   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by intrigeri):

 * Attachment "tor-launcher-clock_skew.png" 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] #32438 [Applications/Tor Launcher]: Inconsistent failure-then-success bootstrap behavior with clock set 24h in the past

[Tor Bug Tracker & Wiki]

#32438: Inconsistent failure-then-success bootstrap behavior with clock set 24h 
in
the past
-+-
 Reporter:  intrigeri|  Owner:  brade
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Launcher|Version:
 Severity:  Normal   | Resolution:
 Keywords:  bootstrap, clock-skew, usability,|  Actual Points:
  ux, s8-errors, AffectsTails|
Parent ID:  #23508   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by intrigeri):

 * Attachment "tor-launcher-clock_skew.log" 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] #32438 [Applications/Tor Launcher]: Inconsistent failure-then-success bootstrap behavior with clock set 24h in the past

[Tor Bug Tracker & Wiki]

#32438: Inconsistent failure-then-success bootstrap behavior with clock set 24h 
in
the past
-+-
 Reporter:  intrigeri|  Owner:  brade
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Launcher   |   Keywords:  bootstrap, clock-skew,
 Severity:  Normal   |  usability, ux, s8-errors,
 |  AffectsTails
Actual Points:   |  Parent ID:  #23508
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Context: I'm investigating which part of Tails' crazy clock fixing dance
 we can remove thanks to
 https://trac.torproject.org/projects/tor/ticket/24661. Corresponding Tails
 ticket: https://redmine.tails.boum.org/code/issues/16471.

 Environment: Tor Browser 9.0.1 x86_64 on Debian unstable, clock set 24h
 before UTC. Tested both with direct connection to the Tor network and with
 bridges.

 The first time I click "Connect" in Tor Launcher, I see a bootstrapping
 error (see attached screenshot and Tor logs):

 {{{
 Tor failed to establish a Tor network connection.

 Loading authority certificates failed (Clock skew -81944 in microdesc
 flavor consensus from CONSENSUS - ?).
 }}}

 I guess that's kind of expected despite the improvements implemented as
 part of https://trac.torproject.org/projects/tor/ticket/24661.

 But then, if I click "Reconfigure" and then "Connect", tor bootstraps
 successfully. This surprises me and feels inconsistent: the way I see it,
 either the clock is skewed enough for tor to fail bootstrapping, and then
 it should not succeed on second try; or tor can somehow deal with skewed
 clock, and then it should succeed on first try.

--
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