chore: create backup container signing keys #232
Draft
Conversation
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
These keys will be unused until a time when we need to rotate. We need to be certain this change doesn't break anything, since it could cause failed updates.
private key is in shared vault and accessible for actions to sign via org-wide secret: `SIGNING_SECRET_BACKUP`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes ublue-os/main#703
These keys will be unused until a time when we need to rotate. When we do need to rotate, we can change the priv key in GitHub Actions, and these will be accepted by the signing policy.
We need to be certain this change doesn't break anything, since it could cause failed updates, though since all changes are in /etc, it should be easy enough to test.
TODO: