[tor-bugs] #21813 [Core Tor/Tor]: create a JSON-based alternative control port protocol

[Tor Bug Tracker & Wiki]

#21813: create a JSON-based alternative control port protocol
-----------------------------+----------------------------------
 Reporter:  arthuredelstein  |          Owner:
     Type:  enhancement      |         Status:  new
 Priority:  Medium           |      Milestone:  Tor: unspecified
Component:  Core Tor/Tor     |        Version:
 Severity:  Normal           |     Resolution:
 Keywords:                   |  Actual Points:
Parent ID:                   |         Points:
 Reviewer:                   |        Sponsor:
-----------------------------+----------------------------------
Changes (by nickm_mobile):

 * milestone:   => Tor: unspecified


Comment:

 I think if someone wants to pursue this, the best way would be to separate
 the encoding/decoding of control messages from acting on and generating
 them, so that they could each be parsed and encoded separately from its
 implementation.  This would probably want to be a machine-generated or
 automated thing, so that we can have less message-specific parsing code,
 not more.  This might also help formalize the informal meta-format of the
 control port by giving it a mapping to json.

 cypherpunks:

 Our main reason for not going with an "internal filter" for the control
 port is that we aren't convinced that there _is_ a useful safe subset of
 the control protocol's functionality.  Nearly all control port commands
 are potentially dangerous if used by a hostile party.

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