Add support for RFC 9180 KEM #339
Merged
Conversation
This file contains 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.
see #333
Add support for the DHKEM(X25519, HKDF-SHA256) KEM from the HPKE RFC. Support for the HPKE functions Seal/Open can be added using this.
TODO:
zeroize()calls where secret have been stored.[ ] Fuzzing targets: There seem to be no other crates available on crates.io that expose the DHKEM functionality that we do here. Those crates that have it internally are HPKE crates, and leave the KEM operations internal. The fuzzing targets will have to be added once full HPKE support has been added as well.