Fully implement hashed signing#9
Merged
bitbeans merged 2 commits intobitbeans:masterfrom Nov 17, 2025
Merged
Conversation
Introduce new methods for creating, loading and validating hashed signatures.
Set hashed signatures as default for signing and validating signatures. The validation process can recognize the signing method and selects the correct validation method.
Owner
|
Thank you very much, it looks great. |
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
2 participants
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.
Also implements hashed signing and sets this as the default procedure. This means that the library behaves exactly like the original
minisign.Signatures are automatically recognized and verified according to their type (hashed/legacy). There is also the option to explicitly choose one type or the other.
We could consider setting this status to version 1.0.0 at this point. What do you think?