This repository was archived by the owner on Jan 19, 2025. It is now read-only.
Feat: Add stricter key validation #4
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
…ing the sequoia_policy_config crate.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Changes:
Check the validity period of all keys (optional)
Set the maximum allowed key validity in
config.toml:If no configuration exists or the value is zero,
Simple WKDwill omit the check.Set the allowed ciphers and hash algorithms in a toml configuration file.
The filepath is specified in the environment variable SEQUOIA_CRYPTO_POLICY or the file
/etc/crypto-policies/back-ends/sequoia.configis used if it exists.Otherwise it uses the sequoia standard policy like previously.
For more details see the documention of sequoia_policy_config and the provided example policy file.
Check subkeys against the policy