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.
Bug 1898924 - openldap behaviour change: TLS certificate chain is ignored by openssl code
Summary: openldap behaviour change: TLS certificate chain is ignored by openssl code
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: openldap
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: LDAP Maintainers
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-18 10:37 UTC by Graham Leggett
Modified: 2022-05-18 07:27 UTC (History)
0 users

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-18 07:27:32 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1578438 0 unspecified CLOSED openldap TLS is not sending the intermediate cert after update 2021-12-10 16:09:59 UTC
Red Hat Bugzilla 1771979 0 medium CLOSED NSS no longer sends intermediate client certificates in TLS if the intermediate certificates are not explicitly trusted 2021-05-17 07:33:51 UTC

Description Graham Leggett 2020-11-18 10:37:49 UTC
Description of problem:

After the switch of crypto library in openldap from NSS to openssl, the behaviour of intermediate certificates has changed.

Where previously a certificate and chain would be read from the certificate PEM file or NSS database automatically, the openldap code in the openssl case reads the certificate only and ignores the rest of the certificates in the chain.

This causes outages when machines are upgraded from pre-rhel7.5 to rhel7.5 or higher through routine patching.

Version-Release number of selected component (if applicable):

RHEL7.5 and up.

How reproducible:

Always.

Steps to Reproduce:
1. Deploy an LDAP infrastructure that uses client certificates with intermediate certificates using pre RHEL7.5 versions of code.
2. Conduct routine patch.
3.

Actual results:

Outage - SSL connections that previously worked now fail with "untrusted certificate" errors.

Expected results:

Patching doesn't take out a whole platform.

Additional info:

The problem exists in openldap on this line:

https://github.com/openldap/openldap/blame/b06f5b0493937fc28f2cc86df1d7f464aa4504d8/libraries/libldap/tls_o.c#L387

To fix this problem, use SSL_CTX_use_certificate_chain_file() as recommended by OpenSSL.

Comment 2 RHEL Program Management 2022-05-18 07:27:32 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.