Repository navigation
crypto.ecdsa: fix handling sign with custom_hash - #23619
Merged
Merged
Conversation
|
Connected to Huly®: V_0.6-22043 |
spytheman
approved these changes
Jan 31, 2025
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
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 small PR following previously already merged PR in fix-no-hash commit.
The current handling with custom hash was still contains some bogus thing without additional test (sorry, its my bad).
Its resolved in the current PR, by the way with:
.reset()on the custom hash before writing messages.write()before.sum()..its does not matching to expected result, when compared, for examples digest produced withsha256.sum256(message)directly. The equivalent ofsum(message)wasThanks ...