Opened 4 weeks ago

Last modified 4 weeks ago

#23677 new defect

Tor should log what it thinks the time is sometime(s)

Reported by: pastly Owned by:
Priority: Medium Milestone: Tor: 0.3.3.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: bootstrap clock-skew ux
Cc: catalyst 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 (3)

comment:1 Changed 4 weeks ago by pastly

Description: modified (diff)

comment:2 Changed 4 weeks ago by catalyst

Cc: catalyst added
Keywords: bootstrap clock-skew ux added

comment:3 Changed 4 weeks ago by catalyst

The tor logging code already prepends a local timestamp when logging to a file, so if someone's disclosing their logs, they're already disclosing their local time if we're reading the log file in close to real time. If we start logging tor's idea of UTC time, we can infer the time zone from a single line in a past log file. I don't know if any users rely on a delay in making their log files available as a means of obscuring their time zone.

Note: See TracTickets for help on using tickets.