Single hop onion service denial of service issues

This is a parent ticket for all single hop anti-DoS mitigation we want to put in Tor. Not only that but it should be seen as "any client single hop" hidden service requests rather than tor2web specific.

Child tickets are really the meat of the work so anything related to this topic should have a child ticket and this parent ticket should not be used for discussions.

changed milestone to %Tor: 0.4.2.x-final

added 034-removed-20180328 034-triage-20180328 component::core tor/tor milestone::Tor: 0.4.2.x-final network-team-roadmap-august owner::dgoulet parent::29999 points::3 priority::medium resolution::fixed severity::normal sponsor::27-must status::closed tor-dos tor-hs tor2web type::enhancement labels

Trac:
Keywords: N/A deleted, 034-triage-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

Trac:
Keywords: N/A deleted, 034-removed-20180328 added

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

Trac:
Milestone: Tor: 0.3.4.x-final to Tor: unspecified

Trac:
Points: N/A to 3

Trac:
Sponsor: N/A to Sponsor27-must
Parent: N/A to #29999 (moved)

Is this still about tor2web? If so, I thought we'd stopped supporting that.

Trac:
Description: This is a parent ticket for all tor2web anti-DoS mitigation we want to put in Tor. Not only that but it should be seen as "any client single hop" hidden service requests rather than tor2web specific.

Child tickets are really the meat of the work so anything related to this topic should have a child ticket and this parent ticket should not be used for discussions.

to

This is a parent ticket for all single hop anti-DoS mitigation we want to put in Tor. Not only that but it should be seen as "any client single hop" hidden service requests rather than tor2web specific.

Child tickets are really the meat of the work so anything related to this topic should have a child ticket and this parent ticket should not be used for discussions.
Summary: Tor2web denial of service issues to Single hop onion service denial of service issues

Add keyword to tickets in network team's roadmap.

Trac:
Keywords: N/A deleted, network-team-roadmap-2019-Q1Q2 added

We'll aim for 042 considering so far the child tickets have code and are relatively simple to fix.

Trac:
Owner: N/A to dgoulet
Milestone: Tor: unspecified to Tor: 0.4.2.x-final
Status: new to accepted

Trac:
Keywords: network-team-roadmap-2019-Q1Q2 deleted, network-team-roadmap-august added

Child tickets have been merged.

Trac:
Status: accepted to closed
Resolution: N/A to fixed

closed

changed time estimate to 24h

mentioned in issue #31754 (moved)

mentioned in issue #29999 (moved)

moved to tpo/core/tor#24962 (closed)

mentioned in issue tpo/core/tor#31754 (closed)