Single Underscore in Option Name
Config options either start with zero or double underscores with a single exception...
>>> conn.getInfo("version")
'0.2.2.23-alpha (git-b85eb949b528f4d7)'
>>> print "\n".join(sorted(conn.getInfo("config/names", "").split("\n")))
...
WarnPlaintextPorts CommaList
WarnUnsafeSocks Boolean
_UsingTestNetworkDefaults Boolean
__AllDirActionsPrivate Boolean
__DisablePredictedCircuits Boolean
__HashedControlSessionPassword LineList
__LeaveStreamsUnattached Boolean
__ReloadTorrcOnSIGHUP BooleanI asked about this on irc, but I'm not clear from Robert's response if this means that '_UsingTestNetworkDefaults' actually shouldn't be exposed to the controller.
08:12 < atagar> I'm finding that most private options start with a double underscore, but in one case it's a single underscore... [bit removed since trac chokes on the double underscores] 08:12 < atagar> is this a mistake? 08:13 < rransom> _UsingTestNetworkDefaults is a fake option. 08:13 < rransom> The double-underscore options are for use by controllers. 08:18 < atagar> Fake option? Not following - the single underscore has some special meaning? 08:18 < rransom> atagar: _UsingTestNetworkDefaults is clobbered within Tor every time it processes its options. 08:19 < rransom> The double-underscore options are actual options that can be set from outside Tor. 08:20 < atagar> Is it right then for _UsingTestNetworkDefaults to be presented via 'GETINFO config/names'? I'm pretty sure this makes it user setable. 08:20 < atagar> yup, it does
Feel free to close if presenting the _UsingTestNetworkDefaults option this way is intended (though I'd be a little curious then what the single underscore should signify for controllers).
Cheers! -Damian