fix(clearsign): Enforce acceptable hash functions in clearsign #281
+144
−16
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
2 tasks
lubux
force-pushed
the
fix/clearsign-check-hash
branch
from
31919f1 to
6956452
Compare
lubux
force-pushed
the
fix/clearsign-check-hash
branch
from
6956452 to
c97e6fa
Compare
lubux
force-pushed
the
fix/clearsign-check-hash
branch
from
c97e6fa to
9cd4c3a
Compare
twiss
approved these changes
May 21, 2025
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.
This PR fixes clearsign to only allow hash functions that are allowed for the particular signing algorithm.