Add secrets.keys_dir config option.
#4877
Open
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
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.
Implements the
secrets.keys_dirconfig option as an alternative tosecrets.keys. Contains unit tests and documentation.Currently managing MAS key material is intertwined with managing MAS configuration: it is not possible to provide signing keys to MAS without some prior knowledge of their content, filename or count. This PR resolves that limitation by introducing the
secrets.keys_dirconfig option.The
secrets.keys_dirconfig option allows specifying a single directory that is expected to contain one file per MAS signingkey. The key files are read from the directory when aKeyStoreis created viaSecretsConfig::key_store().Requires #4876 to derive a key’s kid.