crypto.hmacSha256: add hmac-sha256 signing primitive#102
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
crypto.hmacSha256(key, data)— computes HMAC-SHA256 ofdatausingkey, returns a 64-character lowercase hex string. Uses OpenSSL's single-shotHMAC()function (already linked via-lcrypto). Covers the most common use cases: webhook signature verification and JWT signing.Test plan
npm testpasses (279/279, including newhmac sha256fixture)"key", data="The quick brown fox jumps over the lazy dog"→f7bc83f430538424b13298e6aa6fb143ef4d59a14946175997479dbc2d1a3cd8npm run verify:quickself-hosting passes