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:
Description: Even if a SSL cipher is disabled the server still attempts
to locate the cipher in the security library. If the disabled
cipher is unknown it logs a warning ast server startup, but
if it's disabled there is no reason to check if it exists.
https://fedorahosted.org/389/ticket/48743
Build tested:
389-ds-base-1.3.5.10-5.el7.x86_64
Verification steps:
1. Setup RHDS
2. Enable SSL/TLS as per the Admin Guide sec. 7.4 using the Admin Console
3. Use the default ciphers as part of the SSL/TLS enablement (fortezza family is enabled)
4. Check errors log for SSL alert about fortezza:
[root@rhel-dev slapd-rhel-dev]# grep fortezza /var/log/dirsrv/slapd-rhel-dev/errors
[29/Jul/2016:15:57:44.470979041 +0200] SSL alert: Cipher suite fortezza_null is not available in NSS 3.21. Ignoring fortezza_null
[29/Jul/2016:15:57:44.504161610 +0200] SSL alert: Cipher suite fortezza is not available in NSS 3.21. Ignoring fortezza
[29/Jul/2016:15:57:44.509658458 +0200] SSL alert: Cipher suite fortezza_rc4_128_sha is not available in NSS 3.21. Ignoring fortezza_rc4_128_sha
5. Disable fortezza family using the Admin Console
6. Check errors log for SSL alert about fortezza:
[root@rhel-dev slapd-rhel-dev]# grep fortezza /var/log/dirsrv/slapd-rhel-dev/errors
[root@rhel-dev slapd-rhel-dev]# echo $?
1
Result: server doesn't check for disabled ciphers.
Marking as verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2016-2594.html
Description of problem: Description: Even if a SSL cipher is disabled the server still attempts to locate the cipher in the security library. If the disabled cipher is unknown it logs a warning ast server startup, but if it's disabled there is no reason to check if it exists. https://fedorahosted.org/389/ticket/48743