#22042: HSFETCH not followed by HS_DESC_CONTENT event
--------------------------+------------------------------------
Reporter: nickler | Owner: atagar
Type: defect | Status: reopened
Priority: Medium | Milestone: Tor: 0.3.1.x-final
Component: Core Tor/Tor | Version: Tor: 0.2.9.10
Severity: Normal | Resolution:
Keywords: tor-hs | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------+------------------------------------
Changes (by atagar):
* status: closed => reopened
* resolution: not a bug =>
Comment:
> We could think of a new control port HS_DESC event that tells you "No
more HSDir can be used" or something. Let's open a new ticket if we want
that.
Hi David, lets use this ticket for that. According to the spec ("On
success, Tor replies "250 OK" then Tor MUST eventually follow this with
both a HS_DESC and HS_DESC_CONTENT events with the results.") this is a
tor bug.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22042#comment:5>
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
