#19899: prop224: Add a consensus param to enable/disable next gen onion service ------------------------------------------------+-------------------------- Reporter: dgoulet | Owner: dgoulet Type: enhancement | Status: accepted Priority: High | Milestone: Tor: | 0.2.9.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: prop224, tor-hs, TorCoreTeam201608 | Actual Points: Parent ID: #12424 | Points: 1 Reviewer: | Sponsor: | SponsorR-must ------------------------------------------------+--------------------------
Comment (by dgoulet): Replying to [comment:2 nickm]: > What would be so bad if relays stored prop224 descriptors before the rest of this stuff is deployed? Hrm, I would say to avoid for Tor to become an "Internet File System"? :) Ok yes, it's already "possible" with current system but adding an extra one might not be necessary. I'm not strongly against actually but this consensus params is needed anyway as we talked about it before to also be the switch for the removal of v0 and v1 from tor code. It's also a nice safe switch considering the _humongeous-ness_ of this to turn it off in the early days if we happen to do something really bad? A bit like the same we did with shared random, a way for dirauth to turn it off. I'm open here, if we are confident that we can introduce code for prop224 without this switch, no problem with me. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19899#comment:4> 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