tang: fix clevis-encrypt-tang when specifying a SHA-256 thp #305
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
After latchset#264, we have started using SHA-256 for the JWK thumbprints, however an issue was introduced causing clevis to output data to stdout in certain situations which in turn would render the output of the encryption malformed. This commit fixes this issue and updates the tests to catch this scenario.
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.
After #264, we have started using SHA-256 for the JWK thumbprints,
however an issue was introduced causing clevis to output data to stdout
in certain situations which in turn would render the output of the
encryption malformed.
This commit fixes this issue and updates the tests to catch this
scenario.
Fixes: #304