-
Notifications
You must be signed in to change notification settings - Fork 26
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
2940d74
commit 4f8aa6a
Showing
3 changed files
with
93 additions
and
2 deletions.
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
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 |
---|---|---|
@@ -1,5 +1,3 @@ | ||
.. _latest_upgrade_guide: | ||
|
||
Upgrade from 2.10.1 to 2.11.0 | ||
============================= | ||
|
||
|
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 |
---|---|---|
@@ -0,0 +1,92 @@ | ||
.. _latest_upgrade_guide: | ||
|
||
Upgrade from 2.11.0 to 2.11.1 | ||
============================= | ||
|
||
Preparing for the Ubuntu 24.04 (Noble) migration | ||
------------------------------------------------ | ||
|
||
The 2.11.1 release includes a number of features that will help ensure | ||
your SecureDrop server is prepared for the automated migration to Ubuntu 24.04 | ||
(Noble) in early 2025. | ||
|
||
SecureDrop 2.11.1 will automatically run checks to ensure all servers are ready for migration to Ubuntu 24.04 (Noble). If issues are found, a banner will be displayed in the Journalist Interface to both admins and journalists. Administrators are encouraged to review the | ||
:doc:`Ubuntu 24.04 (Noble) migration guide <../admin/maintenance/noble_migration_prep>` | ||
explaining how to resolve any errors and perform any necessary steps before | ||
Jan. 31st, 2025. | ||
|
||
We will have more details on the migration itself early next year. | ||
|
||
Update Servers to SecureDrop 2.11.1 | ||
------------------------------------ | ||
|
||
Servers running Ubuntu 20.04 will be updated to the latest version of SecureDrop | ||
automatically within 24 hours of the release. | ||
|
||
Update Workstations to SecureDrop 2.11.1 | ||
---------------------------------------- | ||
|
||
.. important:: We recommend backing up your workstations prior to | ||
any upgrades. See our :ref:`backup instructions <backup_workstations>` | ||
for more information. | ||
|
||
Update to SecureDrop 2.11.1 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.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.11.1 by clicking "Update Now": | ||
|
||
.. image:: ../images/securedrop-updater.png | ||
|
||
Fallback: Perform 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.11.1 | ||
|
||
The output should include the following two lines: :: | ||
|
||
gpg: using RSA key 2359E6538C0613E652955E6C188EDD3B7B22E6A3 | ||
gpg: Good signature from "SecureDrop Release Signing Key <[email protected]>" [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.11.1 | ||
|
||
.. important:: If you do see the warning "refname '2.11.1' is ambiguous" in the | ||
output, we recommend that you contact us immediately at [email protected] | ||
(`GPG encrypted <https://securedrop.org/sites/default/files/fpf-email.asc>`__). | ||
|
||
Finally, run the following commands: :: | ||
|
||
sudo apt update | ||
./securedrop-admin setup | ||
./securedrop-admin tailsconfig | ||
|
||
Getting Support | ||
--------------- | ||
|
||
Should you require further support with your SecureDrop installation, we are | ||
happy to help! | ||
|
||
.. include:: ../includes/getting-support.txt |