878e2c5b13
Historically OpenSSL only ever generated DH parameters based on "safe" primes. More recently (in version 1.0.2) support was provided for generating X9.42 style parameter files such as those required for RFC 5114 support. The primes used in such files may not be "safe". Where an application is using DH configured with parameters based on primes that are not "safe" then an attacker could use this fact to find a peer's private DH exponent. This attack requires that the attacker complete multiple handshakes in which the peer uses the same DH exponent. A simple mitigation is to ensure that y^q (mod p) == 1 CVE-2016-0701 (fix part 1 of 2) Issue reported by Antonio Sanso. Reviewed-by: Viktor Dukhovni <viktor@openssl.org> |
||
---|---|---|
.. | ||
dh.h | ||
dh192.pem | ||
dh512.pem | ||
dh1024.pem | ||
dh2048.pem | ||
dh4096.pem | ||
dh_ameth.c | ||
dh_asn1.c | ||
dh_check.c | ||
dh_depr.c | ||
dh_err.c | ||
dh_gen.c | ||
dh_kdf.c | ||
dh_key.c | ||
dh_lib.c | ||
dh_pmeth.c | ||
dh_prn.c | ||
dh_rfc5114.c | ||
dhtest.c | ||
example | ||
generate | ||
Makefile | ||
p192.c | ||
p512.c | ||
p1024.c |