[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #33712 [Core Tor/Tor]: Design a PoW/credential scheme for HS DoS defence
#33712: Design a PoW/credential scheme for HS DoS defence
-------------------------------------------------+-------------------------
Reporter: asn | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone: Tor:
| unspecified
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-hs, tor-dos, network-team- | Actual Points:
roadmap-2020Q1, network-health, research |
Parent ID: #31223 | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by mikeperry):
TL;DR of above is that there are multiple classes of protocol changes, and
I think we should decide our high-level preference for what order we want
to attempt them.
Here's a strawman ordering of the combination of (degree of network
upgrade required, external infra required) pairs:
1. No network upgrade required; no external infra deployment (ie: client
and service only)
2. Backportable network upgrade required; no external infra deployment.
3. No network upgrade required; external infra deployment **is required**.
4. Backportable network upgrade required, external infra deployment **is
required**.
5. Non-backportable IP upgrade required; no external infra deployment.
6. Non-backportable IP upgrade required; external infra deployment **is
required**
7. Non-backportable **full network upgrade**; no external infra
deployment.
8. Non-backportable **full network upgrade**; external infra deployment
**is required**
Important questions to answer:
* Does this ordering sound right in terms of what we should prefer/attempt
to build first?
* Does anyone want to propose a different ordering?
* What sorts of changes are backportable for this problem?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33712#comment:4>
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