[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #29136 [Core Tor/Tor]: PT_LOG and PT_STATUS event fields unspecifed
#29136: PT_LOG and PT_STATUS event fields unspecifed
----------------------------------------+----------------------------------
Reporter: atagar | Owner: ahf
Type: defect | Status: new
Priority: High | Milestone: Tor:
| 0.4.0.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-spec, tor-pt, 040-must | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
----------------------------------------+----------------------------------
Changes (by atagar):
* status: needs_information => new
Comment:
Hi Alex. I'd appreciate if the control-spec includes all information
necessary for parsers. Just about every other event type specifies in
detail what each field within the event will contain...
https://gitweb.torproject.org/torspec.git/tree/control-spec.txt#n3240
https://gitweb.torproject.org/torspec.git/tree/control-spec.txt#n2805
... etc...
PT_LOG and PT_STATUS break this convention by merely describing their
fields. They do not specify what parsers should expect...
https://gitweb.torproject.org/torspec.git/tree/control-spec.txt#n3284
Personally I don't have an interest in what these events do or even if
they're implemented. My sole concern is our spec, as that is what Stem
will implement. If PT_STATUS is moot then lets remove it from the spec.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29136#comment:7>
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