openssl/crypto/dh
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
..
build.info
dh_ameth.c Coverity: fix 1506298: negative returns 2022-07-01 16:36:21 +10:00
dh_asn1.c
dh_backend.c Update copyright year 2022-05-03 13:34:51 +01:00
dh_check.c ossl_dh_check_priv_key: Do not fail on private keys without q 2022-06-15 11:02:30 +02:00
dh_depr.c
dh_err.c
dh_gen.c Use as small dh key size as possible to support the security 2022-07-18 08:06:17 +01:00
dh_group_params.c Use as small dh key size as possible to support the security 2022-07-18 08:06:17 +01:00
dh_kdf.c Remove duplicated #include headers 2022-05-04 13:46:10 +10:00
dh_key.c Update copyright year 2022-05-03 13:34:51 +01:00
dh_lib.c fips module header inclusion fine-tunning 2021-07-06 10:52:27 +10:00
dh_local.h
dh_meth.c
dh_pmeth.c Update our EVP_PKEY_METHODs to get low level keys via public APIs 2021-07-22 13:52:46 +02:00
dh_prn.c
dh_rfc5114.c