Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #13913

Closed (moved)
(moved)
Open
Created Dec 08, 2014 by Damian Johnson@atagar

Undocumented HS behavior with relative paths

Tor accepts relative paths for HiddenServiceDir...

>>> GETCONF HiddenServiceOptions
250-HiddenServiceDir=hidden_service_example
250 HiddenServicePort=80 127.0.0.1:5000

This seems to result in the HiddenServiceDir being relative of the tor process' cwd, rather than the DataDir which I kinda expected. This is all well and good, but should be noted in the manpage.

It's a tiny bit unfortunate that 'GETCONF HidddenServiceOptions' then provides back relative paths, since controllers need to read the HiddenServiceDir to determine the hostname (at least until #1949 (moved)), but not a terribly big whoop. :)

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