[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

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

#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: <https://trac.torproject.org/projects/tor/ticket/24128#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs