Opened 3 years ago

Last modified 17 months ago

#23677 new defect

Tor should log what it thinks the time is sometime(s) — at Version 1

Reported by: pastly Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: bootstrap, clock-skew, ux, 034-triage-20180328, 034-removed-20180328
Cc: catalyst, brade, mcs Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by pastly)

Many issues come from incorrect time/date/timezone settings. And not all the time does Tor log about how it believes the user's clock is wrong by X hours and Y minutes.

For many linux/macos users we can ask them to tell us the output of date -u as a huge troubleshooting help. But not everyone is capable of that. A maybe shouldn't be expected to be.

Two ideas:

  1. Log what Tor thinks the UTC time, local time, and configured timezone are at startup once
  1. Log periodically (say, every HeartbeatPeriod) what Tor thinks [... all the above ...]

Bonus idea:

Can we put the timezone in the log line's timestamp? Would that be enough? Is that dangerous for users? Do we make promises about parse-ability that we'd be breaking?

Child Tickets

Change History (1)

comment:1 Changed 3 years ago by pastly

Description: modified (diff)
Note: See TracTickets for help on using tickets.