Skip to content

LibWeb: Don't import raw X25519 key of incorrect length #5582

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

Merged

Conversation

hopafoot
Copy link
Contributor

Gets 4 more WPT subtests related to rejecting imports of bad X25519 keys in raw format.

wpt tests

Screenshot 2025-07-23 at 3 33 21 PM

@hopafoot hopafoot force-pushed the fix/x25519-bad-length-raw-import branch from 023c6a4 to e8b0fa8 Compare July 25, 2025 16:53
@hopafoot hopafoot force-pushed the fix/x25519-bad-length-raw-import branch from e8b0fa8 to c8c506a Compare July 25, 2025 16:54
@hopafoot hopafoot requested a review from awesomekling July 25, 2025 17:16
Copy link
Member

@ADKaster ADKaster left a comment

Choose a reason for hiding this comment

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

Thanks. We can revisit once w3c/webcrypto#410 is merged

@ADKaster ADKaster enabled auto-merge (rebase) July 25, 2025 19:33
@ADKaster ADKaster disabled auto-merge July 25, 2025 20:19
@ADKaster
Copy link
Member

Well I say that. but can you rebaseline/update the failing test?

Fail: Text/input/wpt-import/WebCryptoAPI/import_export/okp_importKey_failures_X25519.https.any.html

@hopafoot
Copy link
Contributor Author

@ADKaster, done. I think I need approval to rerun CI, though. Sorry for missing this before, this is my first contribution to this project.

@ADKaster ADKaster merged commit 93a0ef9 into LadybirdBrowser:master Jul 26, 2025
8 checks passed
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