Skip to content
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

ML-KEM compatibility #7807

Merged

Conversation

Frauschi
Copy link
Contributor

Hi,

As the WolfSSL implementation of the PQC KEM algorithm Kyber also supports the ML-KEM draft version (enabled by WOLFSSL_ML_KEM), we have to update the groups code points to be compatible with other TLS implementations (e.g. OQS provider).

Also updated the reference to the source of the values to the current OQS GitHub (see here).

Testing has been done using the current master of oqs-provider.

@wolfSSL-Bot
Copy link

Can one of the admins verify this patch?

@dgarske
Copy link
Contributor

dgarske commented Jul 30, 2024

Thank you @Frauschi ! Okay to test. Contributor agreement on file.

@dgarske
Copy link
Contributor

dgarske commented Jul 31, 2024

Retest this please

As the WolfSSL implementation of the PQC KEM algorithm kyber also
supports the ML-KEM draft version (enabled by `WOLFSSL_ML_KEM`), we have
to update the groups code point to be compatible with other TLS
implementations (e.g. OQS provider).

Also updated the reference to the source of the values to the current
OQS Github.

Signed-off-by: Tobias Frauenschläger
<[email protected]>
Copy link
Contributor

@dgarske dgarske left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@anhu to finalize.

@anhu
Copy link
Member

anhu commented Aug 14, 2024

Yep, I double checked against the oqs provider docs. It matches.

@anhu anhu merged commit 8b57e3e into wolfSSL:master Aug 14, 2024
122 checks passed
@Frauschi Frauschi deleted the mlkem_compat branch August 19, 2024 05:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants