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 2002496 - redhat-release should ship public secureboot certs in a well-known location
Summary: redhat-release should ship public secureboot certs in a well-known location
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: redhat-release
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Stephen Gallagher
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-09 02:14 UTC by Brian Stinson
Modified: 2022-05-17 15:36 UTC (History)
4 users (show)

Fixed In Version: redhat-release-9.0-2.6.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 15:35:34 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1997343 1 unspecified CLOSED centos-release should ship public secureboot certs in a well-known location 2022-06-10 20:01:09 UTC
Red Hat Issue Tracker RHELBLD-7392 0 None None None 2021-09-09 02:16:01 UTC
Red Hat Issue Tracker RHELPLAN-96606 0 None None None 2021-09-09 02:33:10 UTC
Red Hat Issue Tracker RTT-3739 0 None None None 2021-09-15 10:44:36 UTC
Red Hat Issue Tracker RTT-3740 0 None None None 2021-09-15 10:44:39 UTC
Red Hat Product Errata RHBA-2022:3893 0 None None None 2022-05-17 15:35:49 UTC

Description Brian Stinson 2021-09-09 02:14:22 UTC 
This is the redhat-release counterpart to: https://bugzilla.redhat.com/show_bug.cgi?id=1997343

We should ship the following certs:

redhatsecurebootca3.cer (s390x CA)
redhatsecurebootca5.cer (x86/aarch64 CA)
redhatsecurebootca6.cer (ppc64le CA)
redhatsecureboot302.cer (s390x kernel signing)
redhatsecureboot501.cer (x86/aarch64 kernel signing)
redhatsecureboot502.cer (x86/aarch64 grub2 signing)
redhatsecureboot503.cer (x86/aarch64 fwupd signing)
redhatsecureboot601.cer (ppc64le kernel signing)
redhatsecureboot602.cer (ppc64le grub2 signing)
Comment 1 Stephen Gallagher 2021-09-09 18:23:33 UTC 
Merge request submitted: https://src.osci.redhat.com/rpms/redhat-release/pull-request/26
Comment 11 errata-xmlrpc 2022-05-17 15:35:34 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 (new packages: redhat-release), 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://access.redhat.com/errata/RHBA-2022:3893
Note You need to log in before you can comment on or make changes to this bug.