Fixed #543 by updating links to tails.net

This commit fixes #543 by replacing references to tails.boum.org with tails.net. As part of the changes with Tails' new domain name and updated documentation, some of the previous documentation links no longer exist. The most notable one is related to Wiping files/drives. This functionality was removed in Tails 6.0, and as a result the documentation has changed to reflect this. Given these changes, this commit also removes references to the Wipe open in files, and instead encourages the use of the Trash can (which is not ideal, and may not actually be good advice).
freedomofpress · May 14, 2024 · 589d87f · 589d87f
1 parent c37ec6f
commit 589d87f
Show file tree

Hide file tree

Showing 30 changed files with 49 additions and 56 deletions.
diff --git a/docs/admin/deployment/onboarding_admins.rst b/docs/admin/deployment/onboarding_admins.rst
@@ -27,8 +27,8 @@ To onboard an additional administrator, you will need:
 
 To set up AW2, follow these steps:
 
-1. Boot AW1, `unlock its persistent volume <https://tails.boum.org/doc/persistent_storage/use/index.en.html>`__,
-   and `set an admin password on the welcome screen <https://tails.boum.org/doc/first_steps/welcome_screen/administration_password/>`__
+1. Boot AW1, `unlock its persistent volume <https://tails.net/doc/persistent_storage/use/index.en.html>`__,
+   and `set an admin password on the welcome screen <https://tails.net/doc/first_steps/welcome_screen/administration_password/>`__
 2. Ensure that Tails and the SecureDrop version on AW1 are up-to-date.
    If not, update now by following the :ref:`most recent upgrade guide <latest_upgrade_guide>`.
 3. Log into the *Journalist Interface* using your admin credentials, and create

diff --git a/docs/admin/deployment/onboarding_journalists.rst b/docs/admin/deployment/onboarding_journalists.rst
@@ -112,8 +112,9 @@ to access the servers over SSH.
   *Journalist Interfaces* are accessible at their v3 addresses via the
   SecureDrop Menu.
 
-- Securely wipe the files on the *Transfer Device*, by right-clicking them
-  in the file manager and selecting **Wipe**.
+- Delete the files on the *Transfer Device* by right-clicking them
+  in the file manager, selecting **Move to Trash**, then navigating to **Trash**
+  in the sidebar and selecting **Empty Trash**.
 
 
 .. warning:: The ``app-journalist.auth_private`` file contains secret

diff --git a/docs/admin/deployment/remote.rst b/docs/admin/deployment/remote.rst
@@ -111,7 +111,7 @@ To create the new SVS USB:
    When you see the welcome dialog, you can proceed without enabling persistence
    or setting an admin password.
 2. Install Tails on the new SVS USB, following the instructions
-   `here. <https://tails.boum.org/install/clone/pc/index.en.html>`_
+   `here. <https://tails.net/install/clone/pc/index.en.html>`_
 3. Boot into the new SVS USB and enable persistence with a strong passphrase
    (a 6-word Diceware passphrase is recommended). In the Persistent volume
    configuration wizard, be sure to enable persistence for “GnuPG - GnuPG

diff --git a/docs/admin/deployment/tails_printing_guide.rst b/docs/admin/deployment/tails_printing_guide.rst
@@ -41,7 +41,7 @@ Installing and Printing via the Tails GUI
 
 Let's look at the flow in Tails 4 for installing a USB-connected printer.
 On the Tails welcome screen, unlock your persistent volume, and
-`set an admin password <https://tails.boum.org/doc/first_steps/welcome_screen/administration_password/>`__.
+`set an admin password <https://tails.net/doc/first_steps/welcome_screen/administration_password/>`__.
 This ensures that you won't have to reinstall the printer each time you start
 Tails.
 

diff --git a/docs/admin/installation/create_usb_boot_drives.rst b/docs/admin/installation/create_usb_boot_drives.rst
@@ -22,7 +22,7 @@ which is needed to install the underlying server OS for your
 Tails Introduction
 ------------------
 
-`Tails <https://tails.boum.org>`__ is a privacy-enhancing live operating
+`Tails <https://tails.net>`__ is a privacy-enhancing live operating
 system that runs on removable media, such as a DVD or a USB stick. It
 sends all your Internet traffic through Tor, does not touch your
 computer's hard drive, and securely wipes unsaved work on shutdown.
@@ -43,15 +43,15 @@ backups, but for now you just need two.
 Install Tails
 ~~~~~~~~~~~~~
 
-The `Tails website <https://tails.boum.org/>`__ has detailed and
+The `Tails website <https://tails.net/>`__ has detailed and
 up-to-date instructions on how to download and verify Tails, and how to
 create a bootable Tails USB drive.
 
 Follow the instructions at these links and then return to this page:
 
 -  `Download and verify the Tails image
-   file <https://tails.boum.org/install/download/index.en.html>`__
--  `Install onto a USB drive <https://tails.boum.org/install/index.en.html>`__
+   file <https://tails.net/install/download/index.en.html>`__
+-  `Install onto a USB drive <https://tails.net/install/index.en.html>`__
 
 .. important:: Make sure you verify the Tails .img file using one of the methods
    described on the Tails website.
@@ -83,7 +83,7 @@ For instructions on how to generate a strong passphrase, see :doc:`the
 Passphrases page <passphrases>`.
 
 Please use the instructions on the `Tails website
-<https://tails.boum.org/doc/persistent_storage/index.en.html>`__
+<https://tails.net/doc/persistent_storage/index.en.html>`__
 to make the persistent volume on each Tails drive you create. When
 creating the persistence volume, you will be asked to select from a
 list of features, such as 'Personal Data'. You should enable **all** features by

diff --git a/docs/admin/installation/hardware.rst b/docs/admin/installation/hardware.rst
@@ -563,7 +563,7 @@ Journalist Workstation and Admin Workstation
 
 Both the *Journalist Workstation* and the *Admin Workstation* must be compatible
 with the Tails operating system. Compare any hardware you want to procure or
-allocate for this purpose against the `list of known issues <https://tails.boum.org/support/known_issues/index.en.html>`__
+allocate for this purpose against the `list of known issues <https://tails.net/support/known_issues/index.en.html>`__
 maintained by the Tails project, but please be advised that the list is far
 from exhaustive.
 

diff --git a/docs/admin/installation/installation_overview.rst b/docs/admin/installation/installation_overview.rst
@@ -114,7 +114,7 @@ you're ready to begin.
           other undocumented solutions.
 
 
-.. _`Tails operating system`: https://tails.boum.org
+.. _`Tails operating system`: https://tails.net
 
 
 .. |SecureDrop architecture overview diagram| image:: ../../diagrams/SecureDrop.png

diff --git a/docs/admin/installation/servers.rst b/docs/admin/installation/servers.rst
@@ -257,7 +257,7 @@ Workstation* was set up with `SSH Client Persistence`_, this key will be saved
 on the *Admin Workstation* and can be used in the future to authenticate to
 the servers in order to perform administrative tasks.
 
-.. _SSH Client Persistence: https://tails.boum.org/doc/persistent_storage/configure/index.en.html#index11h2
+.. _SSH Client Persistence: https://tails.net/doc/persistent_storage/configure/index.en.html#index11h2
 
 First, generate the new SSH keypair:
 

diff --git a/docs/admin/installation/set_up_admin_tails.rst b/docs/admin/installation/set_up_admin_tails.rst
@@ -89,7 +89,7 @@ If you are not copy-pasting this command, we recommend you double-check you have
 entered it correctly before pressing enter. GPG will implicitly verify that the
 fingerprint of the key received matches the argument passed.
 
-.. _Tails is connected to Tor: https://tails.boum.org/doc/anonymous_internet/tor/index.en.html#index5h1
+.. _Tails is connected to Tor: https://tails.net/doc/anonymous_internet/tor/index.en.html#index5h1
 
 If GPG warns you that the fingerprint of the key received does not
 match the one requested, do **not** proceed with the installation. If this

diff --git a/docs/admin/installation/set_up_svs.rst b/docs/admin/installation/set_up_svs.rst
@@ -39,7 +39,7 @@ Tails drive is ready.
 The Tails drive should be clearly labeled “SecureDrop Secure Viewing
 Station”. If it's not labeled, label it right now, then boot it on the
 *Secure Viewing Station*. After it loads, you should see  the Tails
-`Welcome Screen <https://tails.boum.org/doc/first_steps/welcome_screen/index.en.html>`__.
+`Welcome Screen <https://tails.net/doc/first_steps/welcome_screen/index.en.html>`__.
 
 Enter your passphrase to unlock the persistent storage, then press **Unlock**.
 Before starting Tails, set an administration password for use with this Tails

diff --git a/docs/admin/maintenance/backup_and_restore.rst b/docs/admin/maintenance/backup_and_restore.rst
@@ -417,7 +417,7 @@ process.
    **Disks** utility.
 
 .. _contact Support: https://support-docs.securedrop.org/
-.. _an administration password: https://tails.boum.org/doc/first_steps/welcome_screen/administration_password
+.. _an administration password: https://tails.net/doc/first_steps/welcome_screen/administration_password
 
 .. _migrate_v2:
 

diff --git a/docs/admin/maintenance/backup_workstations.rst b/docs/admin/maintenance/backup_workstations.rst
@@ -9,7 +9,7 @@ Backup the Workstations
 .. note::  This workflow will create a single USB drive with the data backed up
  from all Tails drives. If instead you'd like to create a single duplicate
  Tails drive, you should follow the official documentation
- `maintained by the Tails project <https://tails.boum.org/doc/persistent_storage/backup/index.en.html>`_.
+ `maintained by the Tails project <https://tails.net/doc/persistent_storage/backup/index.en.html>`_.
 
 Now that you have set up the *Secure Viewing Station*, the *Admin Workstation*,
 and your *Journalist Workstations*, it is important you make a backup. Your USB

diff --git a/docs/admin/maintenance/update_bios.rst b/docs/admin/maintenance/update_bios.rst
@@ -46,7 +46,7 @@ Intel provides an SHA1 checksum on the download page. Once you have downloaded t
 
 Once you have verified the hash, copy the file to your USB device.
 
-.. _`provides a detailed explanation of this process`: https://tails.boum.org/doc/encryption_and_privacy/checksums/index.en.html
+.. _`provides a detailed explanation of this process`: https://tails.net/contribute/build/reproducible/#index3h1
 
 .. _`on the correct website`: https://downloadcenter.intel.com/
 

diff --git a/docs/admin/maintenance/update_tails_usbs.rst b/docs/admin/maintenance/update_tails_usbs.rst
@@ -15,7 +15,7 @@ they release a new version ahead of the normal cycle in order to address a
 security issue. For regular Tails OS and security information, check out the
 Tails `Security page`_ and subscribe to the Tails RSS/Atom feed.
 
-.. _Security page: https://tails.boum.org/security/index.en.html
+.. _Security page: https://tails.net/security/index.en.html
 
 
 Update via Graphical Installer
@@ -69,7 +69,7 @@ computer and follow the graphical updater prompts that guide you through the
 Alternatively, you can also download and :ref:`install the newest version of Tails from scratch <setup_install_tails>` (as you did when you first installed SecureDrop). This may be faster if your *primary Tails USB* has not been updated in a while,
 and is necessary for Tails releases that do not support automatic updates.
 
-.. _update process: https://tails.boum.org/doc/upgrade/index.en.html
+.. _update process: https://tails.net/doc/upgrade/index.en.html
 
 .. _Step 3:
 
@@ -96,7 +96,7 @@ While writing to the USB disk, Tails may appear to be frozen, or a dialog may ap
 that the application is unresponsive. In the latter case, click **Wait**
 (repatedly if needed) until the operation is complete.
 
-.. _manual update steps: https://tails.boum.org/upgrade/clone/index.en.html
+.. _manual update steps: https://tails.net/upgrade/clone/index.en.html
 
 
 If you encounter issues

diff --git a/docs/admin/reference/admin.rst b/docs/admin/reference/admin.rst
@@ -14,7 +14,7 @@ and Administrator. When possible, we advise having a dedicated
 staff member serving the role of SecureDrop Administrator.
 
 The admin uses a dedicated *Admin Workstation* running 
-`Tails <https://tails.boum.org>`__, connects to the *Application* and
+`Tails <https://tails.net>`__, connects to the *Application* and
 *Monitor Servers* over `authenticated onion services
 <https://tb-manual.torproject.org/onion-services/>`__, and manages them
 using `Ansible <https://www.ansible.com/>`__.

diff --git a/docs/admin/reference/responsibilities.rst b/docs/admin/reference/responsibilities.rst
@@ -168,9 +168,9 @@ Upgrade Documentation`_ on how to upgrade the drives.
 
 .. include:: ../../includes/update-gui.txt
 
-.. _`Tails RSS Feed`: https://tails.boum.org/news/index.en.rss
+.. _`Tails RSS Feed`: https://tails.net/news/index.en.rss
 .. _`Tails
-   Upgrade Documentation`: https://tails.boum.org/doc/upgrade/index.en.html
+   Upgrade Documentation`: https://tails.net/doc/upgrade/index.en.html
 
 .. _monitoring_ossec:
 

diff --git a/docs/images/manual/viewing5.png b/docs/images/manual/viewing5.png
diff --git a/docs/includes/encrypting-drives.txt b/docs/includes/encrypting-drives.txt
@@ -2,7 +2,7 @@
 
    Like all storage media associated with SecureDrop, this drive should be
    encrypted and protected with a secure passphrase. We recommend using the
-   tools built into Tails to `encrypt the drive using LUKS <https://tails.boum.org/doc/encryption_and_privacy/encrypted_volumes/index.en.html>`__.
+   tools built into Tails to `encrypt the drive using LUKS <https://tails.net/doc/encryption_and_privacy/encrypted_volumes/index.en.html>`__.
 
    If you are planning to use hardware RAID and/or hardware-based encryption,
    we recommend that you research Tails compatibility before a procurement

diff --git a/docs/includes/update-gui.txt b/docs/includes/update-gui.txt
@@ -7,4 +7,4 @@ should simply follow the prompts in the updater to perform the update.
   do so, you will need to reboot to enable it.
 
 .. _`Tails Administrator
-   password`: https://tails.boum.org/doc/first_steps/welcome_screen/administration_password/
+   password`: https://tails.net/doc/first_steps/welcome_screen/administration_password/
diff --git a/docs/journalist/documents.rst b/docs/journalist/documents.rst
@@ -55,7 +55,7 @@ Handling File Formats
 ~~~~~~~~~~~~~~~~~~~~~
 
 SecureDrop accepts submissions of any file type. Tails comes with
-`pre-installed applications <https://tails.boum.org/doc/about/features/index.en.html>`__
+`pre-installed applications <https://tails.net/doc/about/features/index.en.html>`__
 for securely working with documents, including an office suite, graphics
 tools, desktop publishing tools, audio tools, and printing and scanning tools.
 
@@ -144,9 +144,8 @@ example, converting a ``.xls`` file to a ``.csv``) to ensure that metadata is
 not left behind in error.
 
 When you no longer need documents, right-click them in the Files application
-and choose **Wipe** to securely delete them.
-
-|Wiping documents|
+and choose **Move to Trash**, then navigate to **Trash** in the sidebar
+and select **Empty Trash**.
 
 .. _`guide to removing metadata`: https://freedom.press/training/everything-you-wanted-know-about-media-metadata-were-afraid-ask/
 
@@ -231,7 +230,7 @@ or via the `support portal <https://support.freedom.press/>`__. Please do **NOT*
 disclose details about the contents of any submission you have received.
 
 .. _`QR codes can contain malicious links`: https://securedrop.org/news/security-advisory-do-not-scan-qr-codes-submitted-through-securedrop-connected-devices
-.. _`working with sensitive documents`: https://tails.boum.org/doc/sensitive_documents/index.en.html
+.. _`working with sensitive documents`: https://tails.net/doc/sensitive_documents/index.en.html
 .. _`Metadata Anonymisation Toolkit 2`: https://mat.boum.org/
 
 Moving Documents to Your Everyday Workstation
@@ -273,8 +272,7 @@ To open the *Export Device* on the *Secure Viewing Station*, follow these steps:
 
 The *Export Device* should now open in the file manager. If there are still
 files on the *Export Device* from your last copy operation,
-`securely delete <https://tails.boum.org/doc/encryption_and_privacy/secure_deletion/index.en.html#index3h1>`__
-them now.
+delete them by moving them to the Trash, and then selecting **Empty Trash**.
 
 Copy the file or files you want to access on your everyday workstation to the
 *Export Device* using the file manager.
@@ -383,8 +381,6 @@ bottom of the page. You will be prompted for confirmation.
 .. |mat2 cli show| image:: ../images/manual/screenshots/mat2_cli_show.png
    :alt: Terminal application displaying the metadata of a file.
 
-.. |Wiping documents| image:: ../images/manual/viewing5.png
-   :alt: Files application displaying the menu that opens after a right-click on a file. The 'Wipe' entry is selected.
 .. |Unlock VeraCrypt| image:: ../images/manual/unlock_veracrypt_in_tails6.png
    :alt: The 'Authentication Required' menu that appears when you plug in a Veracrypt drive. The 'password' box is selected.
    :width: 100%

diff --git a/docs/journalist/svs.rst b/docs/journalist/svs.rst
@@ -50,7 +50,7 @@ behind.
   even if your browser is compromised by malware, attackers cannot easily gain
   access to other data stored on the same computer.
 
-  See the Tails guide to `Browsing the web with Tor Browser <https://tails.boum.org/doc/anonymous_internet/Tor_Browser/index.en.html>`__
+  See the Tails guide to `Browsing the web with Tor Browser <https://tails.net/doc/anonymous_internet/Tor_Browser/index.en.html>`__
   for more information.
 
 Step 2: Copy the encrypted submission to the *Transfer Device*
@@ -115,10 +115,8 @@ one window to another. A faster method is to drag the file to the
    they could be recoverable in the future.
 
 After successfully copying them to the *Secure Viewing Station*, erase the
-files from your *Transfer Device*. Ensure you're viewing the *Transfer Device* folder, then right click on the files that need removal and click "Wipe" to
-securely delete the files from your device.
-
-|Wiping documents|
+files from your *Transfer Device*. Ensure you're viewing the *Transfer Device* folder, then right click on the files that need removal and click "Move to Trash", then navigate to "Trash" folder in
+the sidebar, and select "Empty Trash".
 
 To decrypt and view documents or messages, return to your **Persistent** folder.
 All key actions are initiated by double-clicking:
@@ -178,8 +176,6 @@ default application.
 
 .. _working_with_documents:
 
-.. |Wiping documents| image:: ../images/manual/viewing5.png
-   :alt: Files application displaying the menu that opens after a right-click on a file. The 'Wipe' entry is selected.
 .. |Load external content| image:: ../images/manual/screenshots/journalist-clicks_on_source_and_selects_documents.png
    :alt: Example source page displaying two files: a document and a message, both selected. A button 'Download Selected' is visible above the list of files.
 .. |Download selected| image:: ../images/manual/tbb_Document5.png

diff --git a/docs/journalist/workstation.rst b/docs/journalist/workstation.rst
@@ -17,7 +17,7 @@ and you are able to access the Tor network reliably, you can accept the defaults
 |Connect to Tor in Tails|
 
 For more information about alternative ways to connect to the Tor network, please
-see the section `"Connecting to the Tor network" <https://tails.boum.org/doc/anonymous_internet/tor/index.en.html>`__
+see the section `"Connecting to the Tor network" <https://tails.net/doc/anonymous_internet/tor/index.en.html>`__
 in the Tails documentation.
 
 .. note::
@@ -50,13 +50,13 @@ Updates" option from the *SecureDrop Menu*.
 .. include:: ../includes/update-gui.txt
 
 .. _`Tails
-   Upgrade Documentation`: https://tails.boum.org/doc/upgrade/index.en.html
+   Upgrade Documentation`: https://tails.net/doc/upgrade/index.en.html
 
 Connecting to the *Journalist Interface*
 ----------------------------------------
 Journalists viewing documents on SecureDrop must connect to the
 *Journalist Interface* using the `Tails operating system
-<https://tails.boum.org/>`__ on a USB drive. As part of your on-boarding, your
+<https://tails.net/>`__ on a USB drive. As part of your on-boarding, your
 admin should have provided you with a Tails drive configured for this purpose,
 known as the *Journalist Workstation* USB drive.
 

diff --git a/docs/source/before_you_submit.rst b/docs/source/before_you_submit.rst
@@ -78,7 +78,7 @@ making these decisions.
    visit regularly.
 
 .. _`Tor Project's website`: https://www.torproject.org/
-.. _`Tails operating system`: https://tails.boum.org/
+.. _`Tails operating system`: https://tails.net/
 .. _`@GetTor_bot on Telegram`: https://t.me/gettor_bot
 
 Choose Who to Submit To

diff --git a/docs/upgrade/2.5.0_to_2.5.1.rst b/docs/upgrade/2.5.0_to_2.5.1.rst
@@ -19,7 +19,7 @@ Using the graphical updater
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 On the next boot of your SecureDrop *Journalist* and *Admin Workstations*,
 the *SecureDrop Workstation Updater* will alert you to workstation updates. You
-must have `configured an administrator password <https://tails.boum.org/doc/first_steps/welcome_screen/administration_password/>`_
+must have `configured an administrator password <https://tails.net/doc/first_steps/welcome_screen/administration_password/>`_
 on the Tails welcome screen in order to use the graphical updater.
 
 Perform the update to 2.5.1 by clicking "Update Now":

diff --git a/docs/upgrade/2.5.1_to_2.5.2.rst b/docs/upgrade/2.5.1_to_2.5.2.rst
@@ -19,7 +19,7 @@ Using the graphical updater
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 On the next boot of your SecureDrop *Journalist* and *Admin Workstations*,
 the *SecureDrop Workstation Updater* will alert you to workstation updates. You
-must have `configured an administrator password <https://tails.boum.org/doc/first_steps/welcome_screen/administration_password/>`_
+must have `configured an administrator password <https://tails.net/doc/first_steps/welcome_screen/administration_password/>`_
 on the Tails welcome screen in order to use the graphical updater.
 
 Perform the update to 2.5.2 by clicking "Update Now":

diff --git a/docs/upgrade/2.5.2_to_2.6.0.rst b/docs/upgrade/2.5.2_to_2.6.0.rst
@@ -35,7 +35,7 @@ Using the graphical updater
 
 On the next boot of your SecureDrop *Journalist* and *Admin Workstations*,
 the *SecureDrop Workstation Updater* will alert you to workstation updates. You
-must have `configured an administrator password <https://tails.boum.org/doc/first_steps/welcome_screen/administration_password/>`_
+must have `configured an administrator password <https://tails.net/doc/first_steps/welcome_screen/administration_password/>`_
 on the Tails welcome screen in order to use the graphical updater.
 
 Perform the update to 2.6.0 by clicking "Update Now":

diff --git a/docs/upgrade/2.6.0_to_2.6.1.rst b/docs/upgrade/2.6.0_to_2.6.1.rst
@@ -30,7 +30,7 @@ Using the graphical updater
 
 On the next boot of your SecureDrop *Journalist* and *Admin Workstations*,
 the *SecureDrop Workstation Updater* will alert you to workstation updates. You
-must have `configured an administrator password <https://tails.boum.org/doc/first_steps/welcome_screen/administration_password/>`_
+must have `configured an administrator password <https://tails.net/doc/first_steps/welcome_screen/administration_password/>`_
 on the Tails welcome screen in order to use the graphical updater.
 
 Perform the update to 2.6.1 by clicking "Update Now":