[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9771 [Torflow]: Torflow logs hint that it's crazily misparsing control protocol lines
#9771: Torflow logs hint that it's crazily misparsing control protocol lines
-------------------------+--------------------
Reporter: arma | Owner: aagbsn
Type: defect | Status: new
Priority: normal | Milestone:
Component: Torflow | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
-------------------------+--------------------
Comment (by aagbsn):
It looks like the TIME_CREATED field is unexpected by pyTorCtl.
torspec.git commit 2f040bc03e61d1eef482e6e170ba9de1a3fd434a adds new
fields
The _decode1 function in pytorctl/TorCtl.py isn't very flexible and
doesn't comply with the control spec:
" Clients SHOULD NOT depend on the order of keyword=value arguments,
and SHOULD NOT depend on there being no new keyword=value arguments
appearing between existing keyword=value arguments, though as of this
writing (Jun 2011) some do.
"
So, I guess we've known about this for some time :\
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9771#comment:1>
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