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

update liboqs to version 0.12.0 and use ml-kem instead of kyber #8440

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

vaf-hub
Copy link
Contributor

@vaf-hub vaf-hub commented Jan 30, 2025

kyber will be dropped with the next release

we need to apply our hack to turn ml-kem into kyber for backward compatibility. this requires some extra kdf and hash step to bind the key to the ciphertext.

we do not want to pull additional dependencies in typescript and liboqs already comes with shake and sha3, so we just do this in C.

we apply a patch to remove fprintf calls from the compiledd liboqs code to not depend on stdio for wasm build

#tutadb1956

@vaf-hub vaf-hub requested a review from charlag January 30, 2025 16:06
@vaf-hub vaf-hub force-pushed the crypto/update-liboqs-1956 branch from 94e9b88 to de632d5 Compare January 30, 2025 16:09
Copy link
Contributor

@charlag charlag left a comment

Choose a reason for hiding this comment

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

it seems fine but I wish we didn't have to do nay of this. Good job fixing it.

@vaf-hub vaf-hub force-pushed the crypto/update-liboqs-1956 branch 2 times, most recently from 584543f to 57c908c Compare February 3, 2025 11:30
sarashub and others added 2 commits February 3, 2025 12:50
kyber will be dropped with the next release

we need to apply our hack to turn ml-kem into kyber for backward compatibility. this requires some extra kdf and hash step to bind the key to the ciphertext.

we do not want to pull additional dependencies in typescript and liboqs already comes with shake and sha3, so we just do this in C.

we apply a patch to remove fprintf calls from the compiledd liboqs code to not depend on stdio for wasm build

#tutadb1956
@vaf-hub vaf-hub force-pushed the crypto/update-liboqs-1956 branch from 57c908c to e393084 Compare February 3, 2025 11:51

console.log("Building dev for", app)

if (clean) {
await runStep("Clean", async () => {
await fs.emptyDir(buildDir)
await fs.rm(liboqsIncludeDir, { recursive: true, force: true })
Copy link
Contributor

Choose a reason for hiding this comment

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

this will cause make to bulid every time if I understand it right

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.

3 participants