---------- Forwarded message ---------- From: Domingo Kiser <domingo.ki...@gmail.com> Date: Mon, 15 Jun 2009 16:00:20 -0700 Subject: DH prime over 1024 bits capped by OpenSSL? To: openssl-users@openssl.org
Hello, Does the "SSL_EXPORT_PKEYLENGTH" macro defined in "ssl_locl.h" force non-export ciphers to always use a diffie-hellman prime parameter of 1024 bits? This seems to be the case and I've noticed this behavior in a callback function registered with "SSL_CTX_set_tmp_dh_callback". The "s3_srvr.c" file uses this macro for the third argument to a callback function if its registered and dh params are not part of the certificate stored in the ssl structure. If this is the case, when would the "dh2048.pem" provided in the distribution ever be used? Is there a general rule of thumb on matching dh param sizes with key sizes? I assumed matching the key size would work. I am using DHE-RSA 2048 bit keys with a 2048 bit dh prime. I am failing due to a missing dh parameter, which is the correct behavior in my case due to OpenSSL asking for a 1024 bit parameter rather than a 2048 bit one. I will be perusing rfc2246 (TLS 1.0 spec) and rfc2631 (diffie-hellman key agreement) in the meantime for more information on why OpenSSL returns 1024 in the aforementioned macro. Could it be as simple as 1024 is could enough so don't bother? Any ideas or links to steer me in the right direction would be much appreciated. Cheers, --Domingo -- Sent from my mobile device -- Sent from my mobile device ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
