Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #28298
Closed (moved) (moved)
Open
Issue created Nov 03, 2018 by Roger Dingledine@arma

Tor 0.3.3.1-alpha resumes allowing RunAsDaemon=1 with relative DataDirectory

In 0.3.2.1-alpha we fixed #22731 (moved) (in commit 6fea44c6): we started refusing to start if RunAsDaemon is set and also any of a variety of config options are set to a relative value.

And then in 0.3.3.1-alpha we did commit 192be006, which split the original options->DataDirectory into a new DataDirectory_option variable.

But warn_about_relative_paths() continues to look at

  n += warn_if_option_path_is_relative("DataDirectory",options->DataDirectory);

and that function is called near the top of options_validate() -- before we call validate_data_directories() which is what populates options->DataDirectory.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking