Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add rpm key import in boostrap package post. There are 3 cases (clean install, upgrade package, uninstall); cover all of them. In a clean install scenario, import the key to the rpm database. In a package upgrade scenario (key bump), remove the old key and import the key again - this may not be needed if upstream changes are incorporated into a version of rpm available in dom0. In uninstall case, remove the key from the rpm database after the package is uninstalled.
See https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/ for guidelines on scriptlet ordering in upgrade, uninstall, etc.
Fixes freedomofpress/securedrop-workstation#423
Test plan
make build-rpm
. Package installs successfully; repo file is present in /etc/yum.repos.d andrpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}-%{RELEASE}\t%{SUMMARY}\n' | grep 'SecureDrop Release Signing Key'
shows an entry corresponding to our release signing key in the rpm db.