Red Hat Bugzilla – Bug 439383
rhn_register is very unspecific about problems with the RHN certificate
Last modified: 2015-03-22 21:09:04 EDT
Description of problem:
On a system with badly adjusted date and time (the one in question is on "Sun
Feb 11 08:28:54 CET 2007", don't ask), rhn_register fails to validate the RHN
certificate because it is not yet valid (Systems with date and time in the
future would probably show similar symptoms). Unfortunately, the error message
shown doesn't help a bit, but you need to use a browser, then point it at
https://rhn.redhat.com and get told that the certificate is not yet valid.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set system, to date/time outside the validity range of the RHN certificate
2. rhn_register tell you that it doesn't have a "... security certificate
compatible with https://xmlrpc.rhn.redhat.com/XMLRPC ..." but no details about
3. You're offered to select an SSL certificate from disk, choose
/usr/share/rhn/RHNS-CA-CERT (which comes with the OS)
Incompatible Certificate File
The certificate you provided, /usr/share/rhn/RHNS-CA-CERT, is not compatible
with the Red Hat Network
server at https://xmlrpc.rhn.redhat.com/XMLRPC.You may want to double-check
that you have provided
a valid certificate file. Are you sure you have provided the correct
certificate, and that the certificate
file has not been corrupted?
Please try again with a different certificate file.
"The certificate is only valid from ... to ..., but your system time is set to
... Please ensure you have the correct certificate and your system time is
correct.", possibly offer launching system-config-date.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
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.