[tor-bugs] #18263 [Tor]: GETCONF provides incorrect value when undefined

[Tor Bug Tracker & Wiki]

#18263: GETCONF provides incorrect value when undefined
--------------------+------------------------------------
 Reporter:  atagar  |          Owner:
     Type:  defect  |         Status:  new
 Priority:  Medium  |      Milestone:  Tor: 0.2.8.x-final
Component:  Tor     |        Version:
 Severity:  Minor   |     Resolution:
 Keywords:  easy    |  Actual Points:
Parent ID:          |         Points:
  Sponsor:          |
--------------------+------------------------------------

Comment (by cypherpunks):

 Tor control protocol spec is awfully vague about this.

 Section 3.3 says:
 {{{
   Request the value of a configuration variable.  The syntax is:

     "GETCONF" 1*(SP keyword) CRLF

   If all of the listed keywords exist in the Tor configuration, Tor
 replies
   with a series of reply lines of the form:
       250 keyword=value
   If any option is set to a 'default' value semantically different from an
   empty string, Tor may reply with a reply line of the form:
       250 keyword
 }}}

 "Tor may" or may not. According to this, the problem is/was on your side,
 atagar.

 Also, even if this was instead a MUST, the implication would say:
 ( "option set to default value" AND "that value is semantically different
 from an empty string" ) THEN "reply line omits '=value'"

 Which, aside from leaving one wondering what "semantically different from
 an empty string" precisely means, still allows for an "=" followed by an
 empty value (f.i. if said empty value is not the default).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18263#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online