Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
rhnplugin currently overrides M2Crypto's SSL server name checks with bypass_m2crypto_ssl_connection_check function that always returns True. As code comment suggests, this was added in RHEL-5 in response to bug #332011 to match up2date behaviour in RHEL-4 (which did not perform any name check).
As RHEL-6 uses urlgrabber/pycurl/curl for meta data and package downloads, such workaround will no longer be sufficient for those who needed, as the name check will be preformed and will fail with more confusing error messages.
To test, I configured serverURL to use xmlrpc.rhn name while making sure it still resolves to xmlrpc.rhn.redhat.com IP (e.g. via /etc/hosts entry or domain/search redhat.com in /etc/resolv.conf). I got following error:
# yum list updates
Loaded plugins: rhnplugin
Error: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-i386-server-6. Please verify its path and try again
When cached repomd.xml is already available, error message is bit more helpful:
# yum list updates
Loaded plugins: rhnplugin
Error: failed to retrieve repodata/08277a7eb7d631565a722898328acc33bbb86f4dcd7af3c0e7d6fca0f5d2be41-primary.xml.gz from rhel-i386-server-6
error was [Errno 14] PYCURL ERROR 51 - ""
(See bug #641943 for more discussion on the missing pycurl error message.)
It seems there's not much reason to keep that override when it's no longer of much use.
Version-Release number of selected component (if applicable):
yum-rhn-plugin-0.9.1-5.el6
Additional info:
If RHEL-6 variant of bug #332011 is filed, it may be better to fix it in a way that the check is not bypassed by default.
I removed this override. But this will mean that dual homed RHN Proxies. But that is not supported anyway (see BZ 432058). User will still can use it, but without HTTPS.
Commited to spacewalk.git as commit a239c1ef754cc6149b1bc4af4a6afeb5bb833fed
cherrypicked to satellite.git as commit 5aca297aac12ed6a14b6808f009f2a891b039ead
(In reply to comment #3)
> But this will mean that dual homed RHN Proxies.
Some part of the sentence got lost.
> User will still can use it, but without HTTPS.
I'd expect certificates with multiple host names listed in subject alternate name extension should work too.
But this will mean that dual homed RHN Proxies will stop work. At least if you communicate with them over https. But that is not supported anyway (see BZ 432058). User will still can use it, but without HTTPS.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0565.html