Tomas Mraz ddb13b283b Use as small dh key size as possible to support the security ... Longer private key sizes unnecessarily raise the cycles needed to compute the shared secret without any increase of the real security. We use minimum key sizes as defined in RFC7919. For arbitrary parameters we cannot know whether they are safe primes (we could test but that would be too inefficient) we have to keep generating large keys. However we now set a small dh->length when we are generating safe prime parameters because we know it is safe to use small keys with them. That means users need to regenerate the parameters if they want to take the performance advantage of small private key. Reviewed-by: Kurt Roeckx <kurt@roeckx.be> Reviewed-by: Paul Dale <pauli@openssl.org> Reviewed-by: Hugo Landau <hlandau@openssl.org> (Merged from https://github.com/openssl/openssl/pull/18480)		2022-07-18 08:06:17 +01:00
..
crypto	Pre-declare all core dispatch table functions, and fix the internal ones	2022-07-13 07:56:51 +02:00
internal	Use as small dh key size as possible to support the security	2022-07-18 08:06:17 +01:00
openssl	CMS: add CMS_SignedData_verify(), a variant of CMS_verify() with extensions	2022-07-16 08:15:49 +02:00