Skip to content

Commit

Permalink
Merge pull request #507 from rkraeher/501/document-upgrade-flag-in-ad…
Browse files Browse the repository at this point in the history
…min-ws-guide

Document the upgrade flag in the Admin Workstation troubleshooting guide
  • Loading branch information
nathandyer authored Oct 18, 2023
2 parents 2fc6e3b + ebc20f5 commit 6d2174f
Show file tree
Hide file tree
Showing 3 changed files with 51 additions and 0 deletions.
49 changes: 49 additions & 0 deletions docs/admin/maintenance/update_workstations.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
Troubleshooting Workstation Updates
===================================

This section includes some general troubleshooting instructions for common workstation
update issues. For additional, version-specific issues and recommended actions,
please see the relevant admin upgrade guide.

Performing a manual update
~~~~~~~~~~~~~~~~~~~~~~~~~~
Sometimes, when an update doesn't go according to plan, it's necessary to perform a
manual update and clear the update flag.

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.6.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.6.1

.. important:: If you do see the warning "refname '2.6.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: ::

./securedrop-admin setup
./securedrop-admin tailsconfig
1 change: 1 addition & 0 deletions docs/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -137,6 +137,7 @@ Get Started
admin/maintenance/ossec_alerts
admin/maintenance/backup_and_restore
admin/maintenance/backup_workstations
admin/maintenance/update_workstations
admin/maintenance/update_tails_usbs
admin/maintenance/kernel_troubleshooting
admin/maintenance/rebuild_admin
Expand Down
1 change: 1 addition & 0 deletions update_version.sh
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ readonly OLD_VERSION=$(grep -oP '(?<=^version \= ")\d+\.\d+\.\d+' docs/conf.py)

sed -i "s@$(echo "${OLD_VERSION}" | sed 's/\./\\./g')@$NEW_VERSION@g" docs/admin/installation/set_up_admin_tails.rst
sed -i "s@$(echo "${OLD_VERSION}" | sed 's/\./\\./g')@$NEW_VERSION@g" docs/admin/maintenance/backup_and_restore.rst
sed -i "s@$(echo "${OLD_VERSION}" | sed 's/\./\\./g')@$NEW_VERSION@g" docs/admin/maintenance/update_workstations.rst
sed -i "s@$(echo "${OLD_VERSION}" | sed 's/\./\\./g')@$NEW_VERSION@g" docs/conf.py
sed -i "s@$(echo "${OLD_VERSION}" | sed 's/\./\\./g')@$NEW_VERSION@g" pyproject.toml

Expand Down

0 comments on commit 6d2174f

Please sign in to comment.