#8203: Inconsistent stream events when resolving hostname
------------------------------------------------------+---------------------
Reporter: Desoxy | Owner:
Type: defect | Status:
needs_revision
Priority: normal | Milestone: Tor:
0.2.4.x-final
Component: Tor | Version:
Keywords: tor-client controller dns 024-deferrable | Parent:
Points: | Actualpoints:
------------------------------------------------------+---------------------
Comment(by atagar):
Hi Desoxy, looks good to me! I like the STREAM events you're proposing. It
_might_ be possible that a controller somewhere relies on new streams
having a NEW StreamStatus, but I'm not aware of any (and would probably be
a bug on their part).
I'm less clear on why you want to omit SOURCE_ADDR when issued via RESOLVE
- that would require a small note to be added to the control-spec, but
otherwise I'm fine with it.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8203#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
