Upgrade from 2.3.1 to 2.3.2

Update Servers to SecureDrop 2.3.2

Your servers will be updated to the latest version of SecureDrop automatically within 24 hours of the release.

Update Workstations to SecureDrop 2.3.2

Note

If you encounter errors with the graphical updater, perform a manual update. This will ensure that you have imported the new SecureDrop release signing key.

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 on the Tails welcome screen in order to use the graphical updater.

Perform the update to 2.3.2 by clicking “Update Now”:

../../_images/securedrop-updater.png

Performing a manual update

If the graphical updater fails and you want to perform a manual update instead, first delete the graphical updater’s temporary flag file, if it exists (the . before securedrop is not a typo):

rm ~/Persistent/.securedrop/securedrop_update.flag

This will prevent the graphical updater from attempting to re-apply the failed update and has no bearing on future updates. You can now perform a manual update by running the following commands:

cd ~/Persistent/securedrop
git fetch --tags
gpg --keyserver hkps://keys.openpgp.org --recv-key \
 "2359 E653 8C06 13E6 5295 5E6C 188E DD3B 7B22 E6A3"
git tag -v 2.3.2

The output should include the following two lines:

gpg:                using RSA key 2359E6538C0613E652955E6C188EDD3B7B22E6A3
gpg: Good signature from "SecureDrop Release Signing Key <securedrop-release-key-2021@freedom.press>" [unknown]

Please verify that each character of the fingerprint above matches what is on the screen of your workstation. A warning that the key is not certified is normal and expected. If the output includes the lines above, you can check out the new release:

git checkout 2.3.2

Important

If you do see the warning “refname ‘2.3.2’ is ambiguous” in the output, we recommend that you contact us immediately at securedrop@freedom.press (GPG encrypted).

Finally, run the following commands:

./securedrop-admin setup
./securedrop-admin tailsconfig

Upgrade to Tails 5.0

Important

You must upgrade your workstations to SecureDrop 2.3.2 by following the steps above before upgrading to Tails 5.0. You can verify the version of SecureDrop by running git status in your ~/Persistent/securedrop directory. The output should include “HEAD detached at 2.3.2”.

Tails 5.0 is the first version of Tails to be based on Debian 11 (“Bullseye”). Among the most noticeable changes is the switch to a new frontend for GnuPG called Kleopatra. Once you upgrade your Secure Viewing Station, you will need to use Kleopatra to open .gpg files. Please see our Journalist Guide for more information.

You must perform the upgrade to Tails 5.0 manually. You need a blank USB drive that you can install Tails 5.0 USB on from scratch. You will use this drive to upgrade your Journalist Workstation(s), your Admin Workstation(s), and your Secure Viewing Station(s).

The persistent storage volumes of your USB drives will be migrated as part of this upgrade, but we still highly recommend backing them up first. Follow the steps for updating Tails manually.

Fore each Journalist and Admin Workstation, perform the following additional steps to complete the upgrade:

  1. Boot the USB drive

  2. On the Tails welcome screen, unlock the persistent volume and configure an administrator password

  3. Open a terminal (Applications ▸ Utilities ▸ Terminal)

  4. Run the following commands:

cd ~/Persistent/securedrop/admin
rm -rf .venv3
cd ..
./securedrop-admin setup

When prompted by Tails to “Install Only Once” or “Install Every Time”, click Install Every Time (this is a change from previous versions of Tails).

Getting Support

Should you require further support with your SecureDrop installation, we are happy to help!

  • Community support is available at https://forum.securedrop.org

  • If you are already a member of our support portal, please don’t hesitate to open a ticket there. If you would like to request access, please contact us at securedrop@freedom.press (GPG encrypted). Note that your ticket will be visible to all support portal users at your organization; if this is a concern, reach out by email to the above address or to a staff member directly.

  • The Freedom of the Press Foundation offers training and priority support services. See https://securedrop.org/priority-support/ for more information.