Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When using DHE based cipher suites, the offered DH parameters by mod_ssl are always 1024 bit sized, even if the certificate used is 2048 bit.
This makes httpd not compliant with NIST SP 800-131A when DHE cipher suite is negotiated since 1st of January this year.
Version-Release number of selected component (if applicable):
mod_ssl-2.2.15-29.el6_4.x86_64
httpd-2.2.15-29.el6_4.x86_64
openssl-1.0.1e-15.el6.x86_64
nss-3.15.1-15.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Generate RSA certificates that are 2048bit long
2. Generate 2048 bit DH parameters, add them to file referenced by SSLCertificateFile
3. Connect using tstclnt -d /etc/pki/nssdb/ -h localhost -p 443 -V ssl3: -o -v
Actual results:
tstclnt: SSL version 3.3 using 256-bit AES with 160-bit SHA1 MAC
tstclnt: Server Auth: 2048-bit RSA, Key Exchange: 1024-bit DHE
Compression: NULL
Expected results:
tstclnt: SSL version 3.3 using 256-bit AES with 160-bit SHA1 MAC
tstclnt: Server Auth: 2048-bit RSA, Key Exchange: 2048-bit DHE
Compression: NULL
(note Key Exchange in second line)
Additional info:
http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf
Httpd should automatically select DH parameters that are at least as long as the RSA keys (see SP 800-131A and SP 800-57 Part 1).
Description of problem: When using DHE based cipher suites, the offered DH parameters by mod_ssl are always 1024 bit sized, even if the certificate used is 2048 bit. This makes httpd not compliant with NIST SP 800-131A when DHE cipher suite is negotiated since 1st of January this year. Version-Release number of selected component (if applicable): mod_ssl-2.2.15-29.el6_4.x86_64 httpd-2.2.15-29.el6_4.x86_64 openssl-1.0.1e-15.el6.x86_64 nss-3.15.1-15.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Generate RSA certificates that are 2048bit long 2. Generate 2048 bit DH parameters, add them to file referenced by SSLCertificateFile 3. Connect using tstclnt -d /etc/pki/nssdb/ -h localhost -p 443 -V ssl3: -o -v Actual results: tstclnt: SSL version 3.3 using 256-bit AES with 160-bit SHA1 MAC tstclnt: Server Auth: 2048-bit RSA, Key Exchange: 1024-bit DHE Compression: NULL Expected results: tstclnt: SSL version 3.3 using 256-bit AES with 160-bit SHA1 MAC tstclnt: Server Auth: 2048-bit RSA, Key Exchange: 2048-bit DHE Compression: NULL (note Key Exchange in second line) Additional info: http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf Httpd should automatically select DH parameters that are at least as long as the RSA keys (see SP 800-131A and SP 800-57 Part 1).