]> git.ipfire.org Git - thirdparty/openssl.git/commit
speed: Increase MAX_SIG_NUM and fix its usage in loopargs_t fields
authorIngo Franzki <ifranzki@linux.ibm.com>
Mon, 23 Jun 2025 11:42:08 +0000 (13:42 +0200)
committerNeil Horman <nhorman@openssl.org>
Thu, 26 Jun 2025 12:04:45 +0000 (08:04 -0400)
commit28a0b9c7974cd99b9bbc503292961db99183b7f9
tree93f5d00acdb743037bdf9534184c3b3c487e4871
parent9276d41b0988c29399bb0bf8604c27a9c5a48a3b
speed: Increase MAX_SIG_NUM and fix its usage in loopargs_t fields

Increase the maximum number of signature algorithms.

With the introduction of the SignMessage and VerifyMessage API with
OpenSSL 3.4 the providers that support combined digest and sign algorithms
register quite a lot more signature algorithms, so the current limit of
111 is hit easily.

While at it correct the definitions of the signature fields within the
loopargs_t structure to use MAX_SIG_NUM instead of MAX_KEM_NUM.

Closes: https://github.com/openssl/openssl/issues/27873
Signed-off-by: Ingo Franzki <ifranzki@linux.ibm.com>
Reviewed-by: Neil Horman <nhorman@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Paul Dale <ppzgs1@gmail.com>
(Merged from https://github.com/openssl/openssl/pull/27878)

(cherry picked from commit 7bdc0d13d2b9ce1c1d0ec1f89dacc16e5d045314)
apps/speed.c