#32040: HS intro padding machine reactivates after receiving INTRODUCE_ACK
-------------------------------------------------+-------------------------
Reporter: asn | Owner: asn
Type: defect | Status:
| assigned
Priority: Medium | Milestone: Tor:
| 0.4.4.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: wtf-pad, padding, circpad- | Actual Points:
researchers-want, 043-deferred |
Parent ID: | Points: 1
Reviewer: | Sponsor:
| Sponsor2
-------------------------------------------------+-------------------------
Comment (by mikeperry):
Ok nice catch on the review. I fixed that double-logic bug and squashed
everything down: https://github.com/mikeperry-
tor/tor/tree/bug30992%2B32040
Note that I stripped down the apply_purpose_mask for intro circs to *only*
include C_INTRODUCING, as this should be the first and only purpose we
want to actually *start* machines for, right? We should not try to jump
into the other purposes to apply a fresh machine, but we should keep an
old run around for:
https://github.com/mikeperry-
tor/tor/commit/551ccc95fb242e27477ec5fcbf0af32a4b0ce761
Is C_INTRODUCING the right start purpose? Or can intro circuits jump in
fully formed at later purposes?
Do we want to do the same thing to rends for symmetry?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32040#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
