Opened 3 years ago

Last modified 22 months ago

#23508 new defect

large clock skews cause numerous bootstrap UX issues

Reported by: catalyst Owned by:
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Major Keywords: bootstrap, clock-skew, usability, ux, 032-unreached, s8-errors
Cc: brade, mcs, intrigeri Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Setting the system clock several hours ahead or behind real time can cause many different bootstrapping problems. Often bootstrapping will get stuck with no obvious way to make progress, and no visible indication of what might actually be wrong. These seem to be lead to a disproportionate number of support requests.

Some examples are:

clock in past:

  • stuck at 40% (Loading authority key certs)

clock in future:

  • stuck at 80% (Connecting to the Tor network)
  • stuck at 85% (Finishing handshake with first hop)

More details and child tickets as I investigate further.

Child Tickets

#23506closedcatalystclock_skew_warning should be a bootstrap eventCore Tor/Tor
#23532closedcatalystNETINFO clock skew detection doesn't work on clientsCore Tor/Tor
#23565newdocument signs of client clock skew to ease troubleshootingCommunity/Tor Support
#32438newbradeInconsistent failure-then-success bootstrap behavior with clock set 24h in the pastCore Tor/Tor

Change History (6)

comment:1 Changed 3 years ago by catalyst

Keywords: clock-skew added

comment:2 Changed 3 years ago by mcs

Cc: brade mcs added

comment:3 Changed 3 years ago by nickm

Keywords: 032-unreached added
Milestone: Tor: 0.3.2.x-finalTor: unspecified

Mark a large number of tickets that I do not think we will do for 0.3.2.

comment:4 Changed 3 years ago by catalyst

Keywords: s8-errors added
Sponsor: Sponsor8-can

comment:5 Changed 2 years ago by intrigeri

Cc: intrigeri added

comment:6 Changed 22 months ago by gaba

Sponsor: Sponsor8-can
Note: See TracTickets for help on using tickets.