[tor-dev] Onion Service v2 Deprecation Timeline
dgoulet at torproject.org
Mon Jun 15 16:34:17 UTC 2020
I will try to make this quick. Deprecation of v2 has already been discussed on
this list  and so this is not about re-creating this discussion but rather
giving you the Tor Project timeline for v2 deprecation.
To very quickly summarize why we are deprecating, in one word: Safety. Onion
service v2 uses RSA1024 and 80 bit SHA1 (truncated) addresses . It also
still uses the TAP  handshake which has been entirely removed from Tor for
many years now _except_ v2 services. Its simplistic directory system exposes
it to a variety of enumeration and location-prediction attacks that give HSDir
relays too much power to enumerate or even block v2 services. Finally, v2
services are not being developed nor maintained anymore. Only the most severe
security issues are being addressed.
That being said, the deprecation timeline is now quite simple because v3 has
reached a good maturity level:
* v3 has been the default since Tor 0.3.5.1-alpha.
* v3 is feature parity with v2.
* v3 now has Onion Balance support 
* Entire network supports v3 since the End-of-Life of 0.2.9.x series earlier
The deprecation to obsolescence timeline:
1) September 15th, 2020
0.4.4.x: Tor will start warning onion service operators and clients that
v2 is deprecated and will be obsolete in version 0.4.6
2) July 15th, 2021
0.4.6.x: Tor will no longer support v2 and will be removed from the code
3) October 15th, 2021
We will release new stable versions for all supported series that will
This effectively means that from _today_ (June 11th 2020), the Internet has
around 15 months to migrate from v2 to v3 once and for all.
We plan to publish a blog post in the coming days/weeks about this
deprecation, in order to inform as many users as possible. It will include the
reasons why, how to migrate and the timeline.
We'll probably run into some difficulties here; no matter how prepared we
think we are, we find that there are always more surprises. Nonetheless, we'll
do our best to fix problems as they come up, and try to make this process as
smooth as possible.
The tor maintainers.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: not available
More information about the tor-dev