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.
We currently have the well-known secureboot certificates available for CentOS Stream and RHEL 9. We should switch to using the pesign targets in CentOS Stream koji so that we sign grub2 correctly.
The CentOS Stream x86_64 build of grub2-2.06-21.el9 reports this:
• pesign -l --in=grubx64.efi
---------------------------------------------
certificate address is 0x7f345acee008
Content was not encrypted.
Content is detached; signature cannot be verified.
The signer's common name is CentOS Secure Boot Signing 202
The signer's email address is security
Signing time: Wed Feb 16, 2022
There were certs or crls included.
---------------------------------------------
The RHEL build of grub2-2.06-21.el9 reports:
• pesign -l --in=grubx64.efi
---------------------------------------------
certificate address is 0x7f1fd07f3008
Content was not encrypted.
Content is detached; signature cannot be verified.
The signer's common name is Red Hat Secure Boot Signing 502
The signer's email address is secalert
Signing time: Wed Feb 16, 2022
There were certs or crls included.
---------------------------------------------
This is what I expected in both cases. Additionally, a host pre-installed with CentOS Stream 9 from the mirrors and manually upgraded to grub2-2.06-21 boots properly and reports the following once booted:
• mokutil --sb-state
SecureBoot enabled
What other cases should we include to consider this VERIFIED?
From my POV that should be enough, as the purpose of the patch is precisely use the correct signing for each system. If the certificates are correct, the machine boots and secureboot status is enabled, should be all round.
What we need is to have this merged in c9s and I need to double check this on my side.
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: grub2), 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:3925