mirror of
https://github.com/torproject/support.git
synced 2024-11-27 03:10:34 +00:00
grammar, layout fixes. remove duplicated info. titles need to be on one line
This commit is contained in:
parent
2a6a5680a8
commit
3ff495f17e
@ -6,8 +6,7 @@ seo_slug: v2-deprecation
|
||||
---
|
||||
description:
|
||||
### How do I know if I'm using v2 or v3 onion services?
|
||||
You can identify v3 onion addresses by their 56 character length, e.g. Tor Project's v2 address:`http://expyuzz4wqqyqhjn.onion/`
|
||||
And Tor Project's v3 address: `http://2gzyxa5ihm7nsggfxnu52rck2vv4rvmdlkiu3zzui5du4xyclen53wid.onion/`
|
||||
You can identify v3 onion addresses by their 56 character length, e.g. Tor Project's v2 address:`http://expyuzz4wqqyqhjn.onion/`, and Tor Project's v3 address: `http://2gzyxa5ihm7nsggfxnu52rck2vv4rvmdlkiu3zzui5du4xyclen53wid.onion/`
|
||||
|
||||
If you're an onion service administrator, you must upgrade to v3 onion services as soon as possible.
|
||||
If you're a user, please ensure that you update your bookmarks to the website's v3 onion addresses.
|
||||
@ -20,23 +19,22 @@ In July 2021, 0.4.6 Tor will no longer support v2 and support will be removed fr
|
||||
|
||||
In October 2021, we will release new Tor client stable versions for all supported series that will disable v2.
|
||||
|
||||
You can read more in the Tor Project's blog post [Onion Service version 2 deprecation timeline](https://blog.torproject.org/v2-deprecation-timeline) for more information.
|
||||
You can read more in the Tor Project's blog post [Onion Service version 2 deprecation timeline](https://blog.torproject.org/v2-deprecation-timeline).
|
||||
|
||||
### Can I keep using my v2 onion address? Can I access my v2 onion after September?
|
||||
Is this a backward-incompatible change?
|
||||
### Can I keep using my v2 onion address? Can I access my v2 onion after September? Is this a backward-incompatible change?
|
||||
|
||||
v2 onion addresses are fundamentally insecure. If you have a v2 onion, we recommend you migrate now.
|
||||
V2 onion addresses are fundamentally insecure. If you have a v2 onion, we recommend you migrate now.
|
||||
This is a backward incompatible change: v2 onion services will not be reachable after September 2021.
|
||||
|
||||
### What is the recommendation for developers to migrate?
|
||||
Any tips on how to spread the new v3 addresses to people?
|
||||
### What is the recommendation for developers to migrate? Any tips on how to spread the new v3 addresses to people?
|
||||
|
||||
In torrc, to create a version 3 address, you simply need to add these two lines.
|
||||
The default version is now set to 3 so you don't need to explicitly set it.
|
||||
In torrc, to create a version 3 address, you simply need to create a new service just as you did your v2 service, with these two lines:
|
||||
|
||||
`HiddenServiceDir /full/path/to/your/hs/v3/directory/`
|
||||
`HiddenServiceDir /full/path/to/your/new/v3/directory/`
|
||||
`HiddenServicePort <virtual port> <target-address>:<target-port>`
|
||||
|
||||
The default version is now set to 3 so you don't need to explicitly set it.
|
||||
Restart tor, and look on your directory for the new address.
|
||||
If you wish to keep running your version 2 service until it is deprecated to provide a transition path to your users, add this line to the configuration block of your version 2 service:
|
||||
|
||||
`HiddenServiceVersion 2`
|
||||
@ -44,7 +42,7 @@ If you wish to keep running your version 2 service until it is deprecated to pro
|
||||
This will allow you to identify in your configuration file which one is which version.
|
||||
|
||||
If you have [Onion-Location](https://community.torproject.org/onion-services/advanced/onion-location/) configured on your website, you need to set the header with your new v3 address.
|
||||
For technical documentation about running onion services, please read the [Onion Services](https://community.torproject.org/onion-services/) page in our Community portal.
|
||||
For technical documentation about running onion services, please read the [Onion Services](https://community.torproject.org/onion-services/) page in our Community portal.
|
||||
|
||||
### I didn't see the announcement, can I get more time to migrate?
|
||||
No, v2 onion connections will start failing nowish, first slowly, then suddenly. It's time to move away.
|
||||
@ -56,7 +54,8 @@ Already, introduction points are not in Tor 0.4.6 anymore, so they will not be r
|
||||
Yes, it will work until the v2 onion address is unreachable.
|
||||
You may want to encourage users to update their bookmarks.
|
||||
|
||||
## Is v3 onion services going to help in mitigating DDoS problems?
|
||||
## Are v3 onion services going to help in mitigating DDoS problems?
|
||||
|
||||
Yes, we are continuously working on improving onion services security.
|
||||
Some of the work we have in our roadmap is [ESTABLISH_INTRO Cell DoS Defense Extension](https://gitweb.torproject.org/torspec.git/tree/proposals/305-establish-intro-dos-defense-extention.txt), [Res tokens: Anonymous Credentials for Onion Service DoS Resilience](https://gitweb.torproject.org/torspec.git/tree/proposals/331-res-tokens-for-anti-dos.md), and [A First Take at PoW Over Introduction Circuits](https://gitweb.torproject.org/torspec.git/tree/proposals/327-pow-over-intro.txt).
|
||||
For an overview about these proposals, read the detailed blog post [How to stop the onion denial (of service)](https://blog.torproject.org/stop-the-onion-denial).
|
||||
|
Loading…
Reference in New Issue
Block a user