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 2052755 - Can't SecureBoot current (20220208) Stream 9 ISO
Summary: Can't SecureBoot current (20220208) Stream 9 ISO
Keywords:
Status: CLOSED DUPLICATE of bug 2027505
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: grub2
Version: CentOS Stream
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-09 23:16 UTC by Jesper Reenberg
Modified: 2022-02-10 01:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-10 01:28:52 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-111750 0 None None None 2022-02-09 23:22:03 UTC

Description Jesper Reenberg 2022-02-09 23:16:53 UTC 
Description of problem:

Trying to boot from CentOS-Stream-9-20220208.1-x86_64-boot.iso, with SecureBoot enabled in a VMware vSphere environment fails with a "0x1A Security Violation"


Version-Release number of selected component (if applicable):

CentOS-Stream-9-20220208.1-x86_64-boot.iso


How reproducible:

Steps to Reproduce:
1. Create a new VM
2. Mount the ISO
3. Start the VM

Actual results:

Boot fails.


Expected results:

Boot succeeds and start the installation.


Additional info:

Bug 2002499 claims this to be fixed (as far as I can tell).  But unpacking the ISO file, and looking at the signature of the `grubx64.efi` file, shows that it is still using the "Red Hat Test Certificate".

Comment 15 of that bug (from end September) mentioned the grub package being in QA.
Is it still awaiting, or did something else happen?

```
$ pesign -i /mnt/EFI/BOOT/grubx64.efi -S
---------------------------------------------
certificate address is 0x7f7634122008
Content was not encrypted.
Content is detached; signature cannot be verified.
The signer's common name is Red Hat Test Certificate
No signer email address.
Signing time: Fri Nov 19, 2021
There were certs or crls included.
---------------------------------------------
certificate address is 0x7f7634122b00
Content was not encrypted.
Content is detached; signature cannot be verified.
The signer's common name is Red Hat Test Certificate
No signer email address.
Signing time: Fri Nov 19, 2021
There were certs or crls included.
---------------------------------------------
```
Comment 1 Brian Stinson 2022-02-10 01:28:52 UTC 

*** This bug has been marked as a duplicate of bug 2027505 ***
Note You need to log in before you can comment on or make changes to this bug.