Add Policy WithKey() for verifing content you know is signed with a key #235
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
Signed-off-by: Zach Steindler <[email protected]>
|
How about adding a brief overview/example of the steps to verify with a key (creating the trusted material and configuring the policy) to the |
Signed-off-by: Zach Steindler <[email protected]>
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.
Summary
To address #105.
Right now, if you have a bundle signed with a key, your verification policy needs to include
WithoutIdentitiesUnsafe. This isn't great though because:WithoutIdentitiesUnsafeRelease Note
WithKey()policy option to require a bundle is signed with a key instead of a certificateDocumentation
N/A