mirrors/ladybird
0
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-08-26 04:07:51 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

LibWeb: Expose support for P-521 in ECDH and ECDSA

Browse source 
Replace all TODOs and FIXMEs requiring P-521 support with actual code
paths that make use of it. Gets a few tests by simply not failing early.
This commit is contained in:
devgianlu 2024-12-13 15:28:33 +01:00 • committed by Ali Mohammad Pur
commit 70db7772b8
Notes: github-actions[bot] 2024-12-14 00:53:16 +00:00
3 changed files with 64 additions and 67 deletions
Download patch file Download diff file Expand all files Collapse all files

6
Tests/LibWeb/Text/expected/wpt-import/WebCryptoAPI/derive_bits_keys/ecdh_bits.https.any.txt
View file

@ -2,8 +2,8 @@ Harness status: OK
Found 40 tests
30 Pass
10 Fail
31 Pass
9 Fail
Pass setup - define tests
Fail P-521 good parameters
Fail P-521 mixed case parameters
@ -17,7 +17,7 @@ Pass P-521 no deriveBits usage for base key
Pass P-521 base key is not a private key
Pass P-521 public property value is a private key
Pass P-521 public property value is a secret key
Fail P-521 asking for too many bits
Pass P-521 asking for too many bits
Pass P-256 good parameters
Pass P-256 mixed case parameters
Pass P-256 short result

28
Tests/LibWeb/Text/expected/wpt-import/WebCryptoAPI/sign_verify/ecdsa.https.any.txt
View file

@ -2,8 +2,8 @@ Harness status: OK
Found 253 tests
193 Pass
60 Fail
205 Pass
48 Fail
Pass setup
Pass ECDSA P-256 with SHA-1 verification
Pass ECDSA P-256 with SHA-256 verification
@ -233,27 +233,27 @@ Fail ECDSA P-521 with SHA-1 - The signature was truncated by 1 byte verification
Fail ECDSA P-521 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-256 verification
Fail ECDSA P-521 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-384 verification
Fail ECDSA P-521 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-512 verification
Fail ECDSA P-521 with SHA-1 - Signature has excess padding verification
Fail ECDSA P-521 with SHA-1 - The signature is empty verification
Fail ECDSA P-521 with SHA-1 - The signature is all zeroes verification
Pass ECDSA P-521 with SHA-1 - Signature has excess padding verification
Pass ECDSA P-521 with SHA-1 - The signature is empty verification
Pass ECDSA P-521 with SHA-1 - The signature is all zeroes verification
Fail ECDSA P-521 with SHA-256 - The signature was truncated by 1 byte verification
Fail ECDSA P-521 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-1 verification
Fail ECDSA P-521 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-384 verification
Fail ECDSA P-521 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-512 verification
Fail ECDSA P-521 with SHA-256 - Signature has excess padding verification
Fail ECDSA P-521 with SHA-256 - The signature is empty verification
Fail ECDSA P-521 with SHA-256 - The signature is all zeroes verification
Pass ECDSA P-521 with SHA-256 - Signature has excess padding verification
Pass ECDSA P-521 with SHA-256 - The signature is empty verification
Pass ECDSA P-521 with SHA-256 - The signature is all zeroes verification
Fail ECDSA P-521 with SHA-384 - The signature was truncated by 1 byte verification
Fail ECDSA P-521 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-1 verification
Fail ECDSA P-521 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-256 verification
Fail ECDSA P-521 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-512 verification
Fail ECDSA P-521 with SHA-384 - Signature has excess padding verification
Fail ECDSA P-521 with SHA-384 - The signature is empty verification
Fail ECDSA P-521 with SHA-384 - The signature is all zeroes verification
Pass ECDSA P-521 with SHA-384 - Signature has excess padding verification
Pass ECDSA P-521 with SHA-384 - The signature is empty verification
Pass ECDSA P-521 with SHA-384 - The signature is all zeroes verification
Fail ECDSA P-521 with SHA-512 - The signature was truncated by 1 byte verification
Fail ECDSA P-521 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-1 verification
Fail ECDSA P-521 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-256 verification
Fail ECDSA P-521 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-384 verification
Fail ECDSA P-521 with SHA-512 - Signature has excess padding verification
Fail ECDSA P-521 with SHA-512 - The signature is empty verification
Fail ECDSA P-521 with SHA-512 - The signature is all zeroes verification
Pass ECDSA P-521 with SHA-512 - Signature has excess padding verification
Pass ECDSA P-521 with SHA-512 - The signature is empty verification
Pass ECDSA P-521 with SHA-512 - The signature is all zeroes verification