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

[tor-bugs] #31081 [Core Tor/Tor]: GETCONF allows zero arguments, contrary to spec

#31081: GETCONF allows zero arguments, contrary to spec
-------------------------------+-----------------------------------
     Reporter:  catalyst       |      Owner:  (none)
         Type:  defect         |     Status:  new
     Priority:  Medium         |  Milestone:  Tor: unspecified
    Component:  Core Tor/Tor   |    Version:
     Severity:  Normal         |   Keywords:  tor-control, tor-spec
Actual Points:                 |  Parent ID:
       Points:  1              |   Reviewer:
      Sponsor:  Sponsor31-can  |
-------------------------------+-----------------------------------
 `control-spec.txt` says `GETCONF` takes at least one argument. Tor
 currently allows there to be zero arguments for `GETCONF`. If there are
 zero arguments, it replies with `250 OK`. A reply with a keyword and no
 `=` can mean that a configuration variable has its default value. We've
 therefore committed to having no configuration variables named `OK`. I
 suppose that's OK.

 Probably the easiest thing to do is to document the existing behavior.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31081>
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