#25552: prop224: Onion service rev counters are useless and actually harmful for scalability -----------------------------------------------+--------------------------- Reporter: asn | Owner: dgoulet Type: defect | Status: | needs_revision Priority: Medium | Milestone: Tor: | 0.3.4.x-final Component: Core Tor/Tor | Version: Tor: | 0.3.1.9 Severity: Normal | Resolution: Keywords: tor-hs prop224 034-roadmap-master | Actual Points: Parent ID: | Points: 4 Reviewer: asn | Sponsor: -----------------------------------------------+--------------------------- Changes (by teor):
* status: needs_review => needs_revision Comment: I'm going to suggest a different strategy: 1. Make v3 onion services use the descriptor generation timestamp for the revision counter 2. Backport this change to all tor versions with v3 onion services (0.3.2 and later) This fix will make v3 onion services scaleable, by allowing multiple services to submit descriptors with a very small probability of revision number collisions. It also retains the property that newer descriptors replace older ones. We can make a separate decision about replay caches on HSDirs. We can make a separate decision about removing the revision counter entirely. If we decide to keep it, we should check that it's a 64-bit field, so it lasts past 2038. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25552#comment:18> 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