Upgrade from 1.1.0 to 1.2.0

Updating Workstations to SecureDrop 1.2.0

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 1.2.0 by clicking “Update Now”:

../_images/securedrop-updater.png

Performing a manual update

If the automated update fails, you can perform a manual update by running the following commands:

cd ~/Persistent/securedrop
git fetch --tags
gpg --keyserver hkps://keys.openpgp.org --recv-key \
 "2224 5C81 E3BA EB41 38B3 6061 310F 5612 00F4 AD77"
git tag -v 1.2.0

The output should include the following two lines:

gpg:                using RSA key 22245C81E3BAEB4138B36061310F561200F4AD77
gpg: Good signature from "SecureDrop Release Signing Key"

Please verify that each character of the fingerprint above matches what on the screen of your workstation. If it does, you can check out the new release:

git checkout 1.2.0

Important

If you do see the warning “refname ‘1.2.0’ 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

Upgrading Tails

If you have already upgraded your workstations to Tails 4, follow the graphical prompts to update to the latest version.

Important

If you are still running Tails 3.x on any workstation, we urge you to update to the Tails 4 series as soon as possible. Tails 3.x is no longer receiving security updates, and is no longer supported by the SecureDrop team. Please see our instructions for upgrading to Tails 4.

Backing Up the Tails Workstations

USB flash drives degrade over time and vary in quality. To ensure continued access to SecureDrop by administrators and journalists, we recommend backing up the Tails Workstations on the occasion of a new SecureDrop release, after you have completed the upgrade process for each drive.

You can use a single storage device for backups of multiple workstations. See our Workstation Backup Guide for more information.

Troubleshooting Kernel Issues

SecureDrop 1.2.0 includes a kernel update on the Application and Monitor Servers from the 4.4 to the 4.14 series. As with all kernel updates, we have extensively tested this update against recommended hardware.

If you are running SecureDrop on hardware that is not officially supported, you may encounter compatibility issues with the new kernel. For example, the servers may not boot, or you may lose network connectivity. If this happens, you can temporarily downgrade to the previous kernel version.

Important

To ensure continued secure operation of your SecureDrop instance, it is of critical importance to resolve any compatibility issues with the new kernel as quickly as possible. If you encounter problems with this update, please get in touch with us urgently, so we can help you run the latest supported kernel version.

For information on how to downgrade to the previous kernel, and for additional troubleshooting information, please see our Kernel Troubleshooting Guide.

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.