#19899: prop224: Add a consensus param to enable/disable next gen onion service --------------------------+------------------------------------------------ Reporter: dgoulet | Owner: dgoulet Type: | Status: new enhancement | Priority: High | Milestone: Tor: 0.2.9.x-final Component: Core | Version: Tor/Tor | Severity: Normal | Keywords: prop224, tor-hs, TorCoreTeam201608 Actual Points: | Parent ID: Points: 1 | Reviewer: Sponsor: | SponsorR-must | --------------------------+------------------------------------------------ We need a consensus parameter that controls the deployment of proposal 224 that is next generation onion service.
Lots of code will go in tor without being used at first so this parameter will tell all the tor out there to start using the new generation onion service. This is especially important before we merge HSDir support (#17238) in order for relay to NOT store 224 descriptors while the rest is under development. I'm thinking `OnionService224=0` (or we can omit 224 here and assume "OnionService" is next gen obviously :). -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19899> 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