Add HKDF_SHA512 support to the HPKE implementation#14395
Merged
reaperhulk merged 1 commit intomainfrom Mar 1, 2026
Merged
Conversation
Extend the HPKE KDF enum with HKDF_SHA512 (ID 0x0003) alongside the existing HKDF_SHA256. The KDF type owns its id() and hash_algorithm() methods, and hkdf_expand takes the hash as an argument so both KEM (SHA256) and HPKE (suite KDF) callers go through the same code path. KEM operations (DHKEM(X25519, HKDF-SHA256)) continue to use SHA-256 per RFC 9180. https://claude.ai/code/session_013bNoRc1A2vwBFC6NZkxCtS
a66418d to
26c3470
Compare
reaperhulk
approved these changes
Mar 1, 2026
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
3 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.
Extend the HPKE KDF enum with HKDF_SHA512 (ID 0x0003) alongside the existing HKDF_SHA256. The KDF type owns its id() and hash_algorithm() methods, and hkdf_expand takes the hash as an argument so both KEM (SHA256) and HPKE (suite KDF) callers go through the same code path. KEM operations (DHKEM(X25519, HKDF-SHA256)) continue to use SHA-256 per RFC 9180.
https://claude.ai/code/session_013bNoRc1A2vwBFC6NZkxCtS