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 1080142 - m2crypto does not support subject alternative name with IP address
Summary: m2crypto does not support subject alternative name with IP address
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: m2crypto
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Miloslav Trmač
QA Contact: Stanislav Zidek
URL: https://github.com/martinpaljak/M2Cry...
Whiteboard:
Depends On:
Blocks: 1284927
TreeView+ depends on / blocked
 
Reported: 2014-03-24 18:25 UTC by Alicja Kario
Modified: 2015-11-24 13:22 UTC (History)
2 users (show)

Fixed In Version: m2crypto-0.21.1-17.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1284927 (view as bug list)
Environment:
Last Closed: 2015-11-19 12:58:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2165 0 normal SHIPPED_LIVE m2crypto update 2015-11-19 11:21:50 UTC

Description Alicja Kario 2014-03-24 18:25:29 UTC
Description of problem:
When m2crypto client connects to a server specified only by IP address, the verification of certificate fails

Version-Release number of selected component (if applicable):
m2crypto-0.21.1-14.el7.x86_64

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

Comment 1 Miloslav Trmač 2014-03-24 23:19:23 UTC
Thanks for the report.  File upstream as well for reference.

Comment 2 Miloslav Trmač 2014-03-24 23:20:24 UTC
(In reply to Miloslav Trmač from comment #1)
> File upstream as well for reference.

"Filed upstream", sorry.

Comment 11 errata-xmlrpc 2015-11-19 12:58:25 UTC
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/RHBA-2015-2165.html


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