-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add v2 deprecation timeline & warnings to docs #5373
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,15 +2,21 @@ SecureDrop v3 Onion Services | |
| ============================ | ||
| Tor onion services provide anonymous inbound connections to websites and other | ||
| servers exclusively over the Tor network. For example, SecureDrop uses onion services | ||
| for the *Journalist* and *Source Interface* websites, as well as for | ||
| for the *Journalist* and *Source Interface* websites, as well as for | ||
| adminstrative access to the servers in SSH-over-Tor mode. | ||
|
|
||
| Previous to the release of SecureDrop 1.0.0, only v2 onion services were available, | ||
| but administrators now have the option of enabling next-generation (v3) onion | ||
| services. V3 onion services use stronger cryptographic primitives than v2 onion | ||
| services, and include redesigned protocols that guard against service | ||
| information leaks on the Tor network. The unique identifier in V3 onion | ||
| addresses is 56 characters long - for example: | ||
| SecureDrop currently supports both the older v2 version of the onion services | ||
| protocol, and the current version, v3. The current version provides stronger | ||
| cryptographic primitives than v2 onion services, and includes redesigned | ||
| protocols that guard against service information leaks on the Tor network. | ||
|
|
||
| Because of these important improvements, the Tor project is | ||
| `deprecating support for v2 onion services <https://blog.torproject.org/v2-deprecation-timeline>`__. | ||
| SecureDrop will remove support for v2 onion services as part of its 2.0.0 | ||
| release, planned for **February 2021**. If you are currently using v2 onion services, | ||
| they will become unreachable at that point. | ||
|
|
||
| The unique identifier in V3 onion addresses is 56 characters long - for example: | ||
|
|
||
| .. code-block:: none | ||
|
|
@@ -23,49 +29,47 @@ such as: | |
| http://secrdrop5wyphb5x.onion/ | ||
| For new SecureDrop instances, it is recommended to | ||
| enable v3 onion services only. For existing instances, migration | ||
| to v3 onion services is recommended, and the ability to run both | ||
| v2 and v3 onion services simultaneously is supported to make the process | ||
| easier. | ||
| .. important:: | ||
|
|
||
| If you are currently advertising a 16-character v2 address like the above | ||
| to your sources, it will become unreachable in February 2021. You must | ||
| update to v3 onion services before then. | ||
|
|
||
| There is no downgrade path from v3 to v2 using the ``securedrop-admin`` | ||
| tool. We recommend that you follow the v2+v3 migration path below, and test v3 | ||
| functionality thoroughly before disabling | ||
| v2 services. | ||
|
|
||
| Migrating from v2 to v3 only or v2+v3 | ||
| ------------------------------------- | ||
|
|
||
| .. important:: In a future release of SecureDrop, v3 onion services will | ||
| be required rather than optional, and there is no automatic | ||
| downgrade path from v3 to v2 using the ``securedrop-admin`` | ||
| tool. It is recommended that you follow the v2+v3 migration | ||
| path and test v3 functionality thoroughly before disabling | ||
| v2 services. | ||
|
|
||
| Preparing for the migration | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
| Before starting the migration process, you should decide whether to move | ||
| Before starting the migration process, you should decide whether to move | ||
| straight to v3 only, or move to v2+v3 temporarily. As the URLs of your onion | ||
| services will change with the move to v3, moving to v2+v3 first will allow | ||
| you to minimize the impact of the migration on sources and journalists. | ||
|
|
||
| URL changes will affect the following: | ||
|
|
||
| - The *Source Interface* address will change - once the migration is complete, | ||
| - The *Source Interface* address will change - once the migration is complete, | ||
| you will need to update your landing page and other resources that reference | ||
| the address, such as your SecureDrop directory entry. | ||
| - *Journalist* and *Admin Workstations* will need to be updated to use the v3 | ||
| addresses of the *Journalist* and *Source Interface*, and the SSH proxy | ||
| addresses of the *Journalist* and *Source Interface*, and the SSH proxy | ||
| services if your instance is using SSH over Tor. | ||
| - If your instance uses HTTPS, you will need to provision a new certificate for | ||
| the v3 *Source Interface* address - this will need to be done `after` the new | ||
| address has been generated. | ||
|
|
||
| .. note:: If your certificate provisioning process requires validation of the | ||
| new v3 domain, you may not be able to complete the v3 migration process | ||
| new v3 domain, you may not be able to complete the v3 migration process | ||
| without first disabling HTTPS for v2. If your instance currently uses | ||
| HTTPS with an EV certificate, please contact us via the `SecureDrop | ||
| support portal`_ or via email to [email protected] | ||
| before proceeding with the migration. Please use `our GPG key`_ for | ||
| support portal`_ or via email to [email protected] | ||
| before proceeding with the migration. Please use `our GPG key`_ for | ||
| any email communication. | ||
|
|
||
| .. _SecureDrop Support Portal: https://securedrop-support.readthedocs.io/en/latest/ | ||
| .. _our GPG key: https://securedrop.org/sites/default/files/fpf-email.asc | ||
|
|
||
|
|
@@ -78,8 +82,8 @@ Before proceeding with the migration, you should also back up the instance and | |
|
|
||
| Enabling v3 onion services | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
| To enable v3 onion services, you will need to run the installation playbook, | ||
| via the ``./securedrop-admin install`` command, and then update the *Admin | ||
| To enable v3 onion services, you will need to run the installation playbook, | ||
| via the ``./securedrop-admin install`` command, and then update the *Admin | ||
| Workstation* with ``./securedrop-admin tailsconfig``. | ||
|
|
||
| - First, boot into the *Admin Workstation* with the persistent volume unlocked | ||
|
|
@@ -88,7 +92,7 @@ Workstation* with ``./securedrop-admin tailsconfig``. | |
| the working directory to the Securedrop application directory: | ||
|
|
||
| .. code:: sh | ||
| cd ~/Persistent/securedrop | ||
| - Verify that SecureDrop version 1.0.0 or greater is available or installed on | ||
|
|
@@ -103,32 +107,32 @@ Workstation* with ``./securedrop-admin tailsconfig``. | |
| using the GUI updater or the command: | ||
|
|
||
| .. code:: sh | ||
| ./securedrop-admin update | ||
| - After updating the latest SecureDrop version, use the following command to | ||
| - After updating the latest SecureDrop version, use the following command to | ||
| update ``securedrop-admin``'s dependencies: | ||
|
|
||
| .. code:: sh | ||
| ./securedrop-admin setup | ||
| - Next, enable v3 onion services (and optionally disable v2 services) using: | ||
|
|
||
| .. code:: sh | ||
| ./securedrop-admin sdconfig | ||
| This command will step through the current instance configuration. None of the | ||
| current settings should be changed. When prompted to enable v2 and v3 | ||
| services, you should choose either ``yes`` to both to use v2 and v3 | ||
| concurrently, or ``no`` to v2 and ``yes`` to v3 to migrate to v3 only. | ||
| current settings should be changed. When prompted to enable v2 and v3 | ||
| services, you should choose either ``yes`` to both to use v2 and v3 | ||
| concurrently, or ``no`` to v2 and ``yes`` to v3 to migrate to v3 only. | ||
|
|
||
| - Once the configuration has been updated, run the installation playbook using | ||
| - Once the configuration has been updated, run the installation playbook using | ||
| the command: | ||
|
|
||
| .. code:: sh | ||
| ./securedrop-admin install | ||
| This will enable v3 onion services on the *Application* and *Monitor Servers*. | ||
|
|
@@ -137,37 +141,37 @@ Workstation* with ``./securedrop-admin tailsconfig``. | |
| to use v3 onion services using the command: | ||
|
|
||
| .. code:: sh | ||
| ./securedrop-admin tailsconfig | ||
| - Next, verify connectivity between the *Admin Workstation* and the SecureDrop | ||
| instance as follows: | ||
|
|
||
| - Use the Source desktop shortcut to connect to the *Source Interface* and | ||
| verify that the new 56-character address is present in the Tor Browser | ||
| - Use the Source desktop shortcut to connect to the *Source Interface* and | ||
| verify that the new 56-character address is present in the Tor Browser | ||
| address bar. | ||
| - Use the Journalist desktop shortcut to connect to the *Journalist Interface* | ||
| and verify that the new 56-character address is present in the Tor Browser | ||
| and verify that the new 56-character address is present in the Tor Browser | ||
| address bar. | ||
| - Use the commands ``ssh app`` and ``ssh mon`` in a terminal to verify | ||
| - Use the commands ``ssh app`` and ``ssh mon`` in a terminal to verify | ||
| SSH access to the *Application* and *Monitor Servers*. | ||
|
|
||
| - Finally, back up the instance and *Admin Workstation* USB. | ||
|
|
||
| (Optional) enabling HTTPS | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
| If your instance serves the *Source Interface* over HTTPS, and you plan to | ||
| continue using HTTPS with v3 onion services, you'll need to provision a | ||
| If your instance serves the *Source Interface* over HTTPS, and you plan to | ||
| continue using HTTPS with v3 onion services, you'll need to provision a | ||
| new certificate for the new v3 address. | ||
|
|
||
| You'll find the new *Source Interface* address in the file: | ||
|
|
||
| .. code-block:: none | ||
| ~/Persistent/securedrop/install_files/ansible-base/app-sourcev3-ths | ||
| Follow the instructions in :doc:`HTTPS on the Source Interface <https_source_interface>` | ||
| to provision and install the new certificate. | ||
| to provision and install the new certificate. | ||
|
|
||
|
|
||
| Updating Workstation USBs | ||
|
|
@@ -180,32 +184,32 @@ so, you should update all workstations to use v3 services as soon as possible. | |
| Journalist Workstation: | ||
| ~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
|
||
| - In the *Admin Workstation* used to enable v3 onion services, copy the | ||
| - In the *Admin Workstation* used to enable v3 onion services, copy the | ||
| following files to an encrypted *Transfer Device*: | ||
|
|
||
| .. code-block:: none | ||
| ~/Persistent/securedrop/install_files/ansible-base/app-sourcev3-ths | ||
| ~/Persistent/securedrop/install_files/ansible-base/app-journalist.auth_private | ||
| - Then, boot into the *Journalist Workstation* to be updated, with the persistent | ||
| - Then, boot into the *Journalist Workstation* to be updated, with the persistent | ||
| volume unlocked and an admin password set. | ||
| - Next, open a terminal via **Applications ▸ System Tools ▸ Terminal** and change | ||
| the working directory to the Securedrop application directory: | ||
|
|
||
| .. code:: sh | ||
| cd ~/Persistent/securedrop | ||
| - Ensure that the SecureDrop application code has been updated to the latest version, | ||
| using either the GUI updater or the ``./securedrop-admin update`` command. | ||
|
|
||
| - Insert the *Transfer Device*. | ||
| Copy the ``app-sourcev3-ths`` and ``app-journalist.auth_private`` files from | ||
| the *Transfer Device* to ``~/Persistent/securedrop/install_files/ansible-base``. | ||
| - Open a terminal and run ``./securedrop-admin tailsconfig`` to update the | ||
|
|
||
| - Open a terminal and run ``./securedrop-admin tailsconfig`` to update the | ||
| SecureDrop desktop shortcuts. | ||
|
|
||
| - Verify that the new 56-character addresses are in use by visiting the *Source* | ||
|
|
@@ -217,7 +221,7 @@ Journalist Workstation: | |
| Admin Workstation: | ||
| ~~~~~~~~~~~~~~~~~~ | ||
|
|
||
| - In the *Admin Workstation* used to enable v3 onion services, copy the | ||
| - In the *Admin Workstation* used to enable v3 onion services, copy the | ||
| following files to an encrypted *Transfer Device*: | ||
|
|
||
| .. code-block:: none | ||
|
|
@@ -228,19 +232,19 @@ Admin Workstation: | |
| ~/Persistent/securedrop/install_files/ansible-base/group_vars/all/site-specific | ||
| If your instance uses SSH over Tor, also copy the following files: | ||
| .. code-block:: none | ||
|
|
||
| .. code-block:: none | ||
| ~/Persistent/securedrop/install_files/ansible-base/app-ssh.auth_private | ||
| ~/Persistent/securedrop/install_files/ansible-base/mon-ssh.auth_private | ||
| - Then, boot into the *Admin Workstation* to be updated, with the persistent | ||
| - Then, boot into the *Admin Workstation* to be updated, with the persistent | ||
| volume unlocked and an admin password set. | ||
| - Next, open a terminal via **Applications ▸ System Tools ▸ Terminal** and change | ||
| the working directory to the Securedrop application directory: | ||
|
|
||
| .. code:: sh | ||
| cd ~/Persistent/securedrop | ||
| - Ensure that the SecureDrop application code has been updated to the latest version, | ||
|
|
@@ -249,11 +253,11 @@ Admin Workstation: | |
| - Insert the *Transfer Device*. | ||
| Copy the ``app-sourcev3-ths``, ``*.auth_private``, and ``tor_v3_keys.json`` files from | ||
| the *Transfer Device* to ``~/Persistent/securedrop/install_files/ansible-base``. | ||
| - Copy the ``site-specific`` file from the *Transfer Device* to | ||
|
|
||
| - Copy the ``site-specific`` file from the *Transfer Device* to | ||
| ``~/Persistent/securedrop/install_files/ansible-base/group_vars/all``. | ||
|
|
||
| - Open a terminal and run ``./securedrop-admin tailsconfig`` to update the | ||
| - Open a terminal and run ``./securedrop-admin tailsconfig`` to update the | ||
| SecureDrop desktop shortcuts. | ||
|
|
||
| - Verify that the new 56-character addresses are in use by visiting the *Source* | ||
|
|
@@ -269,8 +273,8 @@ Admin Workstation: | |
|
|
||
| Updating Source Interface references | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
| In order for sources to find and use the new v3 *Source Interface*, you'll | ||
| need to update your landing page. If your instance details are listed | ||
| In order for sources to find and use the new v3 *Source Interface*, you'll | ||
| need to update your landing page. If your instance details are listed | ||
| anywhere else (for example, in the SecureDrop directory), you should update | ||
| those listings too. | ||
|
|
||
|
|
@@ -287,7 +291,7 @@ Disabling v2 onion services | |
| Once you've successfully enabled v3 onion services, and updated your workstations, | ||
| you should disable v2 onion services altogether. | ||
|
|
||
| First, it's recommended that you coordinate with the journalists using the | ||
| First, it's recommended that you coordinate with the journalists using the | ||
| instance to ensure that any ongoing source conversations are uninterrupted. They | ||
| can use SecureDrop's reply feature to give active sources advance notice of | ||
| the address change. | ||
|
|
@@ -308,18 +312,18 @@ When you're ready, follow the steps below to transition to v3 services only: | |
| - Next, update the application configuration using the command: | ||
|
|
||
| .. code:: sh | ||
| ./securedrop-admin sdconfig | ||
| This command will step through the current instance configuration. When prompted | ||
| you should type ``no`` for v2 services and ``yes`` for v3 services to migrate to | ||
| v3 only. No other settings should be modified. | ||
|
|
||
| - Once the configuration has been updated, run the installation playbook using | ||
| - Once the configuration has been updated, run the installation playbook using | ||
| the command: | ||
|
|
||
| .. code:: sh | ||
| ./securedrop-admin install | ||
| This will disable v2 onion services on the *Application* and *Monitor Servers*. | ||
|
|
@@ -328,7 +332,7 @@ When you're ready, follow the steps below to transition to v3 services only: | |
| to use v3 onion services only using the command: | ||
|
|
||
| .. code:: sh | ||
| ./securedrop-admin tailsconfig | ||
| - Next, verify connectivity between the *Admin Workstation* and the SecureDrop | ||
|
|
@@ -339,6 +343,6 @@ When you're ready, follow the steps below to transition to v3 services only: | |
| - Finally, update your other *Admin Workstations*: from a terminal, run: | ||
|
|
||
| .. code:: sh | ||
| ./securedrop-admin sdconfig # choose "no" for v2, "yes" for v3 | ||
| ./securedrop-admin tailsconfig | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you link "disabling v2 services" to a section in the doc that says how to do this? right now we just have a section on how to enable v3 onion service which somewhere in the middle says:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @creviera, addressed as part of #5379.