summaryrefslogtreecommitdiffstats
path: root/CHANGES.md
diff options
context:
space:
mode:
authorTomas Mraz <tomas@openssl.org>2022-06-06 10:22:00 +0200
committerHugo Landau <hlandau@openssl.org>2022-07-18 08:06:17 +0100
commitddb13b283be84d771deba1e964610b1670641f03 (patch)
treebb021170034f9fcbafbbfd8e46a48b7884aa3d9d /CHANGES.md
parent358103b4a651ab3f392f088d86cd30469dccce2e (diff)
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)
Diffstat (limited to 'CHANGES.md')
-rw-r--r--CHANGES.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/CHANGES.md b/CHANGES.md
index 3ee3b44976..c314581ce7 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -133,6 +133,11 @@ OpenSSL 3.1
*Hugo Landau*
+ * When generating safe-prime DH parameters set the recommended private key
+ length equivalent to minimum key lengths as in RFC 7919.
+
+ *Tomáš Mráz*
+
OpenSSL 3.0
-----------