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:
https://github.com/openssl/openssl/blob/master/crypto/x509v3/v3_alt.c#L183

Registered ID is the only field which doesn't have a colon.   The code in python
https://hg.python.org/releases/2.7.11/file/tip/Modules/_ssl.c#l960 expects all general name string values to be in the form "type:value".  Among other problems, this causes urllib3 to fail to validate certs, which is currently causing problems for OpenShift and its curator component which uses elasticsearch-py which uses urllib3.

A SAN containing the Registered ID field is required in order to use SearchGuard 2.x with Elasticsearch 2.x: https://github.com/floragunncom/search-guard-docs/blob/1a35ec309661f7b8fb1efc2586fc298dcb7cb139/installation.md#generating-a-server-certificate

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

openssl-1.0.1e-51.el7_2.5.x86_64

How reproducible:

Every time when using python ssl and the server cert contains SAN with Registered ID and you are validating the cert.


Steps to Reproduce:
1.Try to convert a cert containing a SAN with a Registered ID field using python ssl getpeercert(False).
2.
3.

Actual results:


Expected results:


Additional info:

I have created a bug for Python, too. https://bugs.python.org/issue27691

Since I'm a maintainer of Python's ssl module and wrote/refactored most of the cert printing code a couple of years ago, I took the liberty and address the issue in Python directly. You may find the patch on Python bug 27691.

I created #1364444 to track the bug in Python.

This issue was not selected to be included either in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small amount of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.