Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #25823

Closed (moved)
Open
Opened Apr 16, 2018 by Taylor Yu@catalyst

Tor Launcher inconsistently sets TZ=UTC for tor process

Some investigations done as part of #25511 (moved) suggest that the first time Tor Launcher runs tor, it either unsets or fails to change TZ. If tor crashes or needs to be restarted for some reason, then it sets TZ=UTC. My summary of one instance of this behavior is at ticket:25511#comment:32.

Tor Launcher should probably leave the time zone alone when starting tor, so tor can detect what local time for the machine is. We should also consider the privacy impact of revealing a user's timezone through logging (see #18112 (moved) for one instance of this concern).

In any case Tor Launcher should probably be consistent about which timezone it starts tor in.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#25823