diff options
author | tb <> | 2025-09-05 11:25:50 +0000 |
---|---|---|
committer | tb <> | 2025-09-05 11:25:50 +0000 |
commit | 3391ce89dec660073cd78f2b759e1b6ed694db25 (patch) | |
tree | aa63560e924958484e83481795d3f953b587fc7a /src/lib/libc/string/memcmp.c | |
parent | 9efa66bc164487616dbc6774e8f3fa925a4cee04 (diff) | |
download | openbsd-3391ce89dec660073cd78f2b759e1b6ed694db25.tar.gz openbsd-3391ce89dec660073cd78f2b759e1b6ed694db25.tar.bz2 openbsd-3391ce89dec660073cd78f2b759e1b6ed694db25.zip |
wycheproof: move ECDSA tests to v1
This excludes the bitcoin tests since our ECDSA_verify() doesn't have the
logic to enforce s < order / 2 to avoid the well-known malleability issue
with secp256k1 that (r, s) is valid if and only if (r, order - s) is valid.
Moreover, add a workaround for overly picky P1363 tests where only
correctly padded P1363 signatures are accepted. As the test authors say
"To our knowledge no standard (i.e., IEEE P1363 or RFC 7515) requires any
explicit checks of the signature size during signature verification."
In fact, the problem really is in the test code, not in libcrypto and
is a bit annoying to fix in a non-silly way.
Diffstat (limited to 'src/lib/libc/string/memcmp.c')
0 files changed, 0 insertions, 0 deletions