onion v2 deprecation plan
come up with a plan and timeline to deprecate onion v2 services.
This should be the meta ticket for all ticket that need to be solved before we can deprecate onion v2 services.
- What are the required milestones?
- What tools depend on onion v2 services?
(random) tentative deprecation date : 2023-12-31
maybe announce it as a tentative date so people depending on onion v2 can speak up about there needs sooner rather than later.
George Kadianakis (asn) wrote: (https://lists.torproject.org/pipermail/tor-dev/2018-April/013107.html ) The first actual step to v2 deprecation, is to make v3 the default version. But to get there, we first need to solve various bugs and issues with the current v3 system (#25552 (moved), #22893 (moved), #23662 (moved), #24977 (moved), etc.). We also need to implement various needed features, like offline keys (#18098 (moved)), client-authorization (#20700 (moved) ; WIP https://github.com/torproject/tor/pull/36), control port commands like HSFETCH (#25417 (moved)) and revive onionbalance for v3. We might also want to consider possible improvements to the UX of long onion names (like #24310 (moved)) (https://blog.torproject.org/cooking-onions-names-your-onions).
After we do most of the above, we can turn the switch to make v3 the default, and then we need to wait some time for most of the users to migrate from v2 to v3. After that we can initiate the countdown, and eventually deprecate v2s for real.
It's hard to provide an actual timeline for the above right now. However, we are currently applying for some onion-service-related grants, and hopefully if we get them we will have the funding to accelerate the development pace.