crypto: Optimize the hmac#25686
Merged
Merged
Conversation
Contributor
|
My own tests against |
spytheman
approved these changes
Nov 8, 2025
spytheman
left a comment
spytheman
left a comment
Contributor
There was a problem hiding this comment.
Thank you @CryingN .
Thank you @tankf33der .
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
4 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.
Without altering the operational logic of HMAC, the computation speed has been optimized, and the block division range has been expanded. A 500,000-cycle test was conducted to compare the time taken by the user for the old HMAC and the new HMAC, as shown below:
The new HMAC function supports calculations with a
blocksize > 256. Using the old HMAC would cause a V panic (although now, the significance of crypto is minor).