-
Notifications
You must be signed in to change notification settings - Fork 7
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
MLKEM FIPS 203 final #131
MLKEM FIPS 203 final #131
Conversation
1. Change API to XOF to accept a single parameter of exactly 34 bytes. 2. Correct order of parameter to calls to XOF to "rho # j # i" as in FIPS 203 FINAL. Signed-off-by: Rod Chapman <rodchap@amazon.com>
… 203 FINAL Signed-off-by: Rod Chapman <rodchap@amazon.com>
…_Encrypt Signed-off-by: Rod Chapman <rodchap@amazon.com>
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.
Thank you for updating the code! I confirmed that the KATs run as-is.
This is now out of alignment with the README
in this directory which points to the initial draft and corresponding KATs, and the PDF of the IPD. I can pop that change into a separate issue for us to handle internally, but you're also welcome to change the links and delete the PDF.
I added the two issues that I think this addresses in the sidebar, please remove them if you think they're not fully covered by this PR. |
Looks good to me. |
I added #135 to follow up on the other issues I noted here. Thanks for the update! |
This PR updates the specification of ML-KEM to meet the final FIPS 203 specification, issued by NIST on 13th August 2024.
Updated KATs from https://github.com/post-quantum-cryptography/KAT/tree/main/MLKEM
run fine with these changes.