]> git.ipfire.org Git - thirdparty/openssl.git/commit
In the RFC6979 test vectors, ensure private keys are correctly encoded
authorAlex Gaynor <alex.gaynor@gmail.com>
Sun, 19 Oct 2025 16:30:09 +0000 (12:30 -0400)
committerMatt Caswell <matt@openssl.org>
Mon, 10 Nov 2025 10:00:33 +0000 (10:00 +0000)
commit1dbe8a6e1c56d010c271a80eafb2c7fd1b92fbda
tree5e8079bc884c65db21202957ab7f610ae22cbb7f
parentc05ea2fdb7f7687c2df1b611ece37be1bd03b011
In the RFC6979 test vectors, ensure private keys are correctly encoded

The encoding of these keys is supposed to have a fixed length based on the curve (this enables constant time processing, see oss-security this week). Several of these have private scalars that have leading 0s, but were encoded with the 0s truncated off. This adds back the 0s.

Reviewed-by: Neil Horman <nhorman@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/28956)
test/recipes/30-test_evp_data/evppkey_ecdsa_rfc6979.txt