Skip to content

Commit

Permalink
Adds migration flag for mailcap-hardening
Browse files Browse the repository at this point in the history
The updater must perform a full state run in order to apply the mailcap
hardening inside AppVM private volumes. Create the necessary
run-everything flag via RPM postinst. The updater logic will
automatically clean up the flags are it runs. We'll need to remove this
logic from postinst in the subsequent release of
'securedrop-workstation-dom0-config', so it doesn't recreate the flag.
  • Loading branch information
Conor Schaefer authored and eloquence committed Mar 10, 2021
1 parent fa60a26 commit 6cf625c
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 3 deletions.
3 changes: 0 additions & 3 deletions dom0/securedrop-check-migration
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,4 @@ if [[ -n "$(qvm-ls --tags sd-workstation --raw-list | perl -nE '/sd-(?!small|lar
reason="template-consolidation"
echo "Migration required for ${reason}, will re-run Salt states."
request_migration "$reason"
else
echo "No migration required, skipping full state run against all VMs."
rm -rf "${flag_dir}"
fi
2 changes: 2 additions & 0 deletions rpm-build/SPECS/securedrop-workstation-dom0-config.spec
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,8 @@ find /srv/salt -maxdepth 1 -type f -iname '*.top' \
| xargs -n1 basename \
| sed -e 's/\.top$$//g' \
| xargs qubesctl top.enable > /dev/null
mkdir -p /tmp/sdw-migrations
touch /tmp/sdw-migrations/mailcap-hardening

%changelog
* Fri Nov 20 2020 SecureDrop Team <securedrop@freedom.press> - 0.5.2
Expand Down

0 comments on commit 6cf625c

Please sign in to comment.