Opened 4 days ago

Last modified 43 hours ago

#31737 new task

Change handling of relative paths in %include directives?

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Description

Right now, relative paths in %include directives are handled relative to Tor's working directory, which doesn't make a lot of sense. Handling them relative to the configuration file might make more sense?

We'd want to figure out a way to handle this that won't break existing users.

Child Tickets

Change History (1)

comment:1 in reply to:  description Changed 43 hours ago by teor

Replying to nickm:

Right now, relative paths in %include directives are handled relative to Tor's working directory, which doesn't make a lot of sense. Handling them relative to the configuration file might make more sense?

We'd want to figure out a way to handle this that won't break existing users.

Try relative to the cwd first, and then try relative to the config file containing the %include directive?

We could also deprecate cwd-relative paths, and warn when they are used.
And then eventually remove them.

If we wanted a simpler change, we could just deprecate and warn on any relative path.

Note: See TracTickets for help on using tickets.