Re: [tor-bugs] #24128 [Core Tor/Tor]: GETCONF doesn't resolve "auto" settings

[Tor Bug Tracker & Wiki]

#24128: GETCONF doesn't resolve "auto" settings
--+
 Reporter:  catalyst  |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  not a bug
 Keywords:  tor-control   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  new => closed
 * resolution:   => not a bug


Comment:

 Closing as not-a-bug.  We could do the getinfo feature at some point in
 the future, if someone wants to put in the effort.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24128 [Core Tor/Tor]: GETCONF doesn't resolve "auto" settings

[Tor Bug Tracker & Wiki]

#24128: GETCONF doesn't resolve "auto" settings
--+
 Reporter:  catalyst  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-control   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by teor):

 Sometimes, "auto" means "try both, and choose whatever works". I'm not
 sure how we represent that.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24128 [Core Tor/Tor]: GETCONF doesn't resolve "auto" settings

[Tor Bug Tracker & Wiki]

#24128: GETCONF doesn't resolve "auto" settings
--+
 Reporter:  catalyst  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-control   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by arma):

 Agreed, getconf should tell you the actual setting string for the config
 option -- if it's auto, then it's auto.

 There are indeed a pile of config options which have different behaviors
 depending on other things. For simple examples, I'm thinking of the ones
 that disable stuff if something else isn't enabled, e.g.
 {{{
 if (options->UseEntryGuards) {
   log_info(LD_CONFIG, "Authoritative directory servers can't set "
"UseEntryGuards. Disabling.");
   options->UseEntryGuards = 0;
 }
 }}}

 I am fine in theory with a getinfo for looking up Tor's "actual" plans for
 various situations. But we might be wise to make some good plan for
 bringing order to the config.c chaos first. :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24128 [Core Tor/Tor]: GETCONF doesn't resolve "auto" settings

[Tor Bug Tracker & Wiki]

#24128: GETCONF doesn't resolve "auto" settings
--+
 Reporter:  catalyst  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-control   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 Right.  It's not clear to me that the GETCONF behavior is even _wrong_
 here: the setting is in fact "auto", not something else.  Some kind of
 standard GETINFO mapping for the as-used value of these options might be
 better?

 e.g., I'm thinking of something like:

 {{{
 GETCONF UseMicrodescriptors
 250 UseMicrodescriptors=auto
 GETINFO config/as-used/UseMicrodescriptors
 250-config/as-used/UseMicrodescriptors=1
 250 OK
 }}}

 (but I'm not at all attached to the "as-used" name)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs