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

Add support for P-384 and P-521, prepare new version #61

Merged
merged 4 commits into from
Jul 11, 2024

Conversation

divergentdave
Copy link
Contributor

An upgrade to hpke 0.12.0 recently landed. This bumps package versions, adds the ability to select the newly supported P-521, and does the same for P-384 as well.

After applying these changes, I am now running into something like WebAssembly/binaryen#6608. Running npm run build hits a segfault in wasm-opt, but if I re-run the command adding the --debug flag, it works. (~/.cache/.wasm-pack/wasm-opt-4d7a65327e9363b7/wasm-opt pkg/node/hpke_dispatch_bg.wasm -o pkg/node/hpke_dispatch_bg.wasm-opt.wasm -O --debug) This will need some sort of upgrade or workaround before we can actually release this.

@divergentdave
Copy link
Contributor Author

Upgrading the wasm-pack NPM dependency indeed fixed this.

@divergentdave divergentdave marked this pull request as ready for review July 10, 2024 20:02
@divergentdave divergentdave requested a review from a team as a code owner July 10, 2024 20:02
@divergentdave
Copy link
Contributor Author

FWIW, the existing test vector test is now automatically testing the P-521 KEM, but no test vectors for P-384 were provided with the spec.

@divergentdave divergentdave merged commit 2780d91 into main Jul 11, 2024
10 checks passed
@divergentdave divergentdave deleted the david/new-version branch July 11, 2024 22:44
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