Opened 7 weeks ago

Last modified 6 weeks ago

#31654 new defect

Should --list-torrc-options and GETINFO config/names have more in common?

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

Description

The --list-torrc-options lists all settable options.

The GETINFO config/names configuration command lists all listed options.

In practice, this means that they differ when it comes to virtual (linelist_v) options like "HiddenServiceOptions" which are listed to the controller, but not settable.

Do we care about this?

The controller is allowed to GETCONF HiddenServiceOptions, but is not allowed to set it. From the command line, there is no way to access it.

Child Tickets

TicketStatusOwnerSummaryComponent
#31706newExpose config flags to the controllerCore Tor/Tor

Change History (4)

comment:1 in reply to:  description Changed 6 weeks ago by teor

Replying to nickm:

In practice, this means that they differ when it comes to virtual (linelist_v) options like "HiddenServiceOptions" which are listed to the controller, but not settable.

The controller is allowed to GETCONF HiddenServiceOptions, but is not allowed to set it. From the command line, there is no way to access it.

Is there any controller command that tells the controller which options it is not allowed to set?

Or does control code that tries to set all options, need to special-case HiddenServiceOptions?

comment:2 Changed 6 weeks ago by nickm

Options are listed along with their types; any options that are listed as Virtual may not be set.

comment:3 Changed 6 weeks ago by nickm

(this is not guaranteed, though. There could be other unsettable options in the future. Probably better to give an official mechanism for this)

comment:4 Changed 6 weeks ago by teor

That's now #31706

Note: See TracTickets for help on using tickets.