Sign apt's Release file with multiple GPG keys #69
Conversation
This file contains hidden or 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
The GPG config option and associated command arguments now accept multiple GPG keys, which are all used to sign the Release file. This makes it easier to roll keys, similar to the Debian archives which are signed with multiple release keys.
Using a space-separated string of GPG UIDs is compatible with non-bash, POSIX compatible shells such as dash.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The GPG config option and associated command arguments now accept
multiple GPG keys, which are all used to sign the Release file. This
makes it easier to roll keys, similar to the Debian archives which are
signed with multiple release keys.