Support for MLKEM-768 keys#655
Closed
john-craig wants to merge 1 commit into
Closed
Conversation
Owner
|
Hi @john-craig, thank you for your PR, but we plan to implement X-Wing hybrid keys instead, using the same HPKE strategy as #651 and C2SP/C2SP#156. We are working on this right now, and will start with the specification, and then land the change once we have two interoperable implementations, along with @str4d. |
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
2 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.
This adds support for using MLKEM-768 keys for deriving the wrapping key used to protected filekeys, as well as unit tests for functionality.