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 1284927 - m2crypto does not support subject alternative name with IP address
Summary: m2crypto does not support subject alternative name with IP address
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: m2crypto
Version: 6.8
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Miloslav Trmač
QA Contact: BaseOS QE Security Team
URL: https://github.com/martinpaljak/M2Cry...
Whiteboard:
Depends On: 1080142
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-24 13:22 UTC by Stanislav Zidek
Modified: 2017-12-06 12:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1080142
Environment:
Last Closed: 2017-12-06 12:14:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Stanislav Zidek 2015-11-24 13:22:26 UTC 
+++ This bug was initially created as a clone of Bug #1080142 +++

Same problem exists in RHEL-6 (m2crypto-0.20.2-9.el6). Problem fixed in upstream. Cloning the bug for reference (see bz1080142#c3).

Description of problem:
When m2crypto client connects to a server specified only by IP address, the verification of certificate fails

How reproducible:
Always

Steps to Reproduce:
1. Create a CA and sing certificate with SAN pointing to 127.0.0.1
2. Start s_server with the certificate
3. connect to local s_server using 127.0.0.1 as the hostname

Actual results:
LOOP: SSL connect: before/connect initialization
LOOP: SSL connect: SSLv2/v3 write client hello A
LOOP: SSL connect: SSLv3 read server hello A
LOOP: SSL connect: SSLv3 read server certificate A
LOOP: SSL connect: SSLv3 read server key exchange A
LOOP: SSL connect: SSLv3 read server done A
LOOP: SSL connect: SSLv3 write client key exchange A
LOOP: SSL connect: SSLv3 write change cipher spec A
LOOP: SSL connect: SSLv3 write finished A
LOOP: SSL connect: SSLv3 flush data
LOOP: SSL connect: SSLv3 read server session ticket A
LOOP: SSL connect: SSLv3 read finished A
INFO: SSL connect: SSL negotiation finished successfully
Traceback (most recent call last):
  File "sni.py", line 48, in <module>
    s.connect((host, port))
  File "/usr/lib64/python2.7/site-packages/M2Crypto/SSL/Connection.py", line 188, in connect
    if not check(self.get_peer_cert(), self.addr[0]):
  File "/usr/lib64/python2.7/site-packages/M2Crypto/SSL/Checker.py", line 98, in __call__
    fieldName='subjectAltName')
M2Crypto.SSL.Checker.WrongHost: Peer certificate subjectAltName does not match host, expected 127.0.0.1, got DNS:wronghostname.com, DNS:example.com, DNS:evenmoreincorrectname.com, IP Address:127.0.0.1
ALERT: write: warning: close notify

Expected results:
Successful connection to server

--- Additional comment from Hubert Kario on 2014-03-31 18:50:48 CEST ---

Issue of course affects all released versions, so after it is implemented upstream, we will have to consider backporting it to earlier releases.
Comment 2 Jan Kurik 2017-12-06 12:14:19 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Note You need to log in before you can comment on or make changes to this bug.