Bug 566479 - RHNS-CA-CERT must contain a certificate valid after 2013
Summary: RHNS-CA-CERT must contain a certificate valid after 2013
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rhn-client-tools
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Milan Zázrivec
QA Contact: Jiri Kastner
URL:
Whiteboard:
Depends On:
Blocks: 569321
TreeView+ depends on / blocked
 
Reported: 2010-02-18 15:25 UTC by Michael Mráka
Modified: 2010-03-30 08:44 UTC (History)
8 users (show)

Fixed In Version: rhn-client-tools-0.4.20-32.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-30 08:44:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
New CA certificate (not new complete file) (5.01 KB, text/plain)
2010-03-01 10:00 UTC, Mark J. Cox
no flags Details
replacement RHNS-CA-CERT file (8.66 KB, application/octet-stream)
2010-03-01 10:04 UTC, Mark J. Cox
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2010:0270 0 normal SHIPPED_LIVE rhn-client-tools bug fix and enhancement update 2010-03-29 15:02:35 UTC

Description Michael Mráka 2010-02-18 15:25:02 UTC
Description of problem:
RHNS-CA-CERT contains CA certificates valid until 2013. Lifetime of RHEL5 probably extends beyond this so we have to include new certificate valid after 2013.
New cert have to have serial != 0.

Version-Release number of selected component (if applicable):
rhn-client-tools-0.4.20-9.el5

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Mark J. Cox 2010-02-18 15:51:12 UTC
Also remove the bad redundant cert

(2nd certificate in the list:

        Validity
            Not Before: Sep  5 20:45:16 2002 GMT
            Not After : Sep  9 20:45:16 2007 GMT

)

Comment 2 Jiri Skrabal 2010-02-22 15:41:10 UTC
Can anyone please generate that certificate? We can probably generate it within our team, but I suppose it is not desired.

Comment 4 Mark J. Cox 2010-02-23 22:40:37 UTC
marked as a blocker with security keyword because this will have a customer impact which could stop customers getting security updates.

If we do not include the new CA then RHEL5.5 will stop accepting updates from RHN in 2013.  Of course we can push a new package to 5.5.z or 5.6 before 2013 with a new CA, but anyone in 2013 who installs from a 5.5 ISO (or previous) will not be able to get any security updates automatically.

Comment 6 Mark J. Cox 2010-02-23 22:45:34 UTC
(note this is RHBA-2009:9254)

Comment 12 Mark J. Cox 2010-03-01 10:00:00 UTC
Created attachment 397017 [details]
New CA certificate (not new complete file)

Comment 13 Mark J. Cox 2010-03-01 10:04:04 UTC
Created attachment 397019 [details]
replacement RHNS-CA-CERT file

Comment 14 Michael Mráka 2010-03-01 10:25:45 UTC
Fixed spacewalk (upstream) version of rhn-client-tools:

commit 31fb4296ee9825469cb6687a84f83b44ad639e10
    Automatic commit of package [rhn-client-tools] release [0.9.4-1].
commit 27474175a8f25d0d62bb28adda181ea2cb5a5f2c
    added new CA key valid until 2020

Comment 15 Michael Mráka 2010-03-01 10:28:34 UTC
Fixed RHEL5.5 version (svn):
------------------------------------------------------------------------
r191147 | mmraka | 2010-03-01 11:22:53 +0100 (Mon, 01 Mar 2010) | 2 lines
removed expired CA certs and added new CA cert valid until 2020

Comment 16 Milan Zázrivec 2010-03-01 12:58:49 UTC
New build containing the new CA certificate: rhn-client-tools-0.4.20-32.el5

QA: Test registration with rhn.redhat.com & SSL enabled.

Comment 20 Mark J. Cox 2010-03-05 18:00:00 UTC
c18: note that "openssl x509" command will only show you the first CA it comes across, not all the CA's that are in the file.  To verify the cert you'd have to cut and paste it out before passing to openssl x509.

Comment 22 errata-xmlrpc 2010-03-30 08:44:42 UTC
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-2010-0270.html


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