[tor-commits] [status-site/main] Adding v2 deprecation incident

anarcat at torproject.org anarcat at torproject.org
Mon May 10 14:36:53 UTC 2021

commit e47d3b3b3dfbfe2a86eb816e05e36c11a6e17ed2
Author: Duncan <duncan at torproject.org>
Date:   Thu May 6 20:44:10 2021 +0000

    Adding v2 deprecation incident
 content/issues/2021-05-6-v2-deprecation.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/content/issues/2021-05-6-v2-deprecation.md b/content/issues/2021-05-6-v2-deprecation.md
new file mode 100644
index 0000000..85c6218
--- /dev/null
+++ b/content/issues/2021-05-6-v2-deprecation.md
@@ -0,0 +1,22 @@
+title: V2 Onion Services Deprecation
+date: 2021-05-06 16:45:00
+resolved: false
+# Possible severity levels: down, disrupted, notice
+severity: notice
+  - v2 Onion Services
+section: issue
+**If you are an onion site administrator, you must upgrade to v3 onion services as soon as possible.**
+As we [announced last year](https://blog.torproject.org/v2-deprecation-timeline), v2 onion services will be deprecated and obsolete in Tor 0.4.6.x. As of April 2021, Tor Browser Alpha uses this version of Tor and v2 addresses no longer work in this and future versions of Tor Browser Alpha.
+When Tor Browser stable moves to Tor 0.4.6.x in October 2021, **v2 onion addresses will be completely unreachable**.
+Why are we deprecating v2 onion services? Safety. Technologies used in v2 onion services are vulnerable to different kinds of attacks, and v2 onion services are no longer being developed or maintained. The new version of onion services provides improved encryption and enhanced privacy for administrators and users.
+It's critical that onion service administrators migrate to v3 onion services and work to inform users about this change as soon as possible.
+[Read more about the deprecation on our blog](https://blog.torproject.org/v2-deprecation-timeline).

More information about the tor-commits mailing list