Re: [tor-bugs] #6239 [Stem]: Implement SETCONF/RESETCONF parsing in Stem

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#6239: Implement SETCONF/RESETCONF parsing in Stem
--------------------+-------------------------------------------------------
 Reporter:  neena   |          Owner:  neena            
     Type:  task    |         Status:  needs_information
 Priority:  normal  |      Milestone:                   
Component:  Stem    |        Version:                   
 Keywords:          |         Parent:                   
   Points:          |   Actualpoints:                   
--------------------+-------------------------------------------------------

Comment(by neena):

 Replying to [comment:5 atagar]:
 > What happens if there are multiple unknown options? Do we then fall
 through to raising a InvalidRequest? What sorts of issues did you see with
 a 513 and 553 status?

 {{{
 setconf test1 test2 test3
 552 Unrecognized option: Unknown option 'test1'.  Failing.
 }}}
 We'll raise InvalidArguments with just the first invalid argument in
 exception.arguments.
 Some examples...
 {{{
 setconf hiddenserviceport="2839 232.23.2.32:7832" hiddenservicedir="/tmp"
 513 Unacceptable option value: Failed to configure rendezvous options. See
 logs for details.
 setconf dirport=abcd
 513 Unacceptable option value: Invalid DirPort/DirListenAddress
 configuration
 setconf disabledebuggerattachment=0
 553 Transition not allowed: While Tor is running, disabling
 DisableDebuggerAttachment is not allowed.
 }}}

 > Good change. Mind changing the other __init__.py files too?
 After this is merged.

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