Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tor-launcher
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • tor-launcher
  • Issues
  • #25823

Closed
Open
Created Apr 16, 2018 by Taylor Yu@catalyst

Tor Launcher inconsistently sets TZ=UTC for tor process

Some investigations done as part of legacy/trac#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 legacy/trac#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 an admin enable hashed storage. More information
Assignee
Assign to
Time tracking