Opened 4 years ago

Closed 4 years ago

#13913 closed defect (fixed)

Undocumented HS behavior with relative paths

Reported by: atagar Owned by:
Priority: Very Low Milestone: Tor: 0.2.6.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: tor-hs documentation easy lorax
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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), but not a terribly big whoop. :)

Child Tickets

Change History (4)

comment:1 Changed 4 years ago by nickm

Keywords: tor-hs documentation easy lorax added
Milestone: Tor: 0.2.???

comment:2 Changed 4 years ago by rl1987

Status: newneeds_review

comment:3 Changed 4 years ago by nickm

Milestone: Tor: 0.2.???Tor: 0.2.6.x-final

comment:4 Changed 4 years ago by nickm

Resolution: fixed
Status: needs_reviewclosed

Merged and tweaked. Thanks!

Note: See TracTickets for help on using tickets.