Bug 1402153 - GENERAL_NAME_print doesn't print colon for Registered ID
Summary: GENERAL_NAME_print doesn't print colon for Registered ID
Alias: None
Product: Fedora
Classification: Fedora
Component: openssl
Version: 24
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2016-12-06 22:55 UTC by Rich Megginson
Modified: 2018-11-09 10:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1364268
Last Closed: 2017-08-08 19:24:51 UTC
Type: Bug

Attachments (Terms of Use)

Description Rich Megginson 2016-12-06 22:55:39 UTC
+++ This bug was initially created as a clone of Bug #1364268 +++

Description of problem:

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):


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).

Actual results:

Expected results:

Additional info:

--- Additional comment from Tomas Mraz on 2016-08-05 03:19:29 EDT ---

Without the fix being in upstream I do not see it getting into RHEL-7.3 update. However I'll chase for upstream acceptance and it should make it into RHEL-7.4.

--- Additional comment from Christian Heimes on 2016-08-05 05:41:18 EDT ---

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

--- Additional comment from Christian Heimes on 2016-08-05 06:59:47 EDT ---

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.

--- Additional comment from Christian Heimes on 2016-08-05 07:11:18 EDT ---

I created #1364444 to track the bug in Python.

Comment 1 Tomas Mraz 2016-12-07 10:38:11 UTC
This is already fixed in 1.1.0 in Rawhide.

Comment 2 Fedora End Of Life 2017-07-26 00:03:15 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-08-08 19:24:51 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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