Size the hash staging buffer to the input and cache the HMAC pads - #103
Merged
Conversation
Both hot paths allocated more than the work required. TransformUntyped and TransformStream sized their staging buffer to the full 64 KB default regardless of input, so hashing a one-byte message (as HKDF does, byte by byte) still cleared a 64 KB buffer; a shared StagingSize helper now clamps the buffer to the actual input length, honouring a user-set BufferSize as the chunk maximum. THMACNotBuildInAdapter recomputed ipad/opad and copied the key on every Initialize — and HKDF re-inits the HMAC for every Extract and Expand block — so an FPadsValid flag now caches the pads and rebuilds them only when the key changes, invalidated on both SetKey and Clear.
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.
Both hot paths allocated more than the work required. TransformUntyped and TransformStream sized their staging buffer to the full 64 KB default regardless of input, so hashing a one-byte message (as HKDF does, byte by byte) still cleared a 64 KB buffer; a shared StagingSize helper now clamps the buffer to the actual input length, honouring a user-set BufferSize as the chunk maximum. THMACNotBuildInAdapter recomputed ipad/opad and copied the key on every Initialize — and HKDF re-inits the HMAC for every Extract and Expand block — so an FPadsValid flag now caches the pads and rebuilds them only when the key changes, invalidated on both SetKey and Clear.