-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception for X25519MLKEM768 naming #27
Conversation
This is not in compliance with -hybrid-design: |
@@ -109,6 +109,10 @@ of the scheme, which will remain more ubiqutous for secp256r1 in the coming year | |||
For this reason we put the ML-KEM shared secret first in X25519MLKEM768, | |||
and the ECDH shared secret first in SecP256r1MLKEM768 and SecP384r1MLKEM1024. | |||
|
|||
Note: The group name X25519MLKEM768 does not adhere to the naming convention outlined in | |||
{{Section 3.2 of hybrid}}. Specifically, the order of shares in the concatenation has been | |||
reversed. This is due to historical reasons. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This situation is unfortunate but I think this direction leaves us with the minimum amount of mess.
Let's merge it as this is current state of the art. |
No description provided.