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.
DescriptionVitaly Kuznetsov
2023-08-10 08:17:05 UTC
RHEL currently ships shim-15.6 which doesn't contain
commit 0eb07e11b20680200d3ce9c5bc59299121a75388
Author: Chris Coulson <chris.coulson>
Date: Tue May 31 22:21:26 2022 +0100
Make SBAT variable payload introspectable
and thus doesn't contain '.sbatlevel' PE section:
$ objdump -h shimx64.efi
shimx64.efi: file format pei-x86-64
Sections:
Idx Name Size VMA LMA File off Algn
0 .eh_frame 0001db1c 0000000000005000 0000000000005000 00000400 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
1 .text 0005e663 0000000000023000 0000000000023000 0001e000 2**4
CONTENTS, ALLOC, LOAD, READONLY, CODE
2 .reloc 0000000a 0000000000082000 0000000000082000 0007c800 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
3 .data.ident 00000049 0000000000084000 0000000000084000 0007ca00 2**4
CONTENTS, ALLOC, LOAD, DATA
4 .data 0002d5b4 0000000000085000 0000000000085000 0007cc00 2**4
CONTENTS, ALLOC, LOAD, DATA
5 .vendor_cert 0000037c 00000000000b3000 00000000000b3000 000aa200 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
6 .dynamic 00000100 00000000000b4000 00000000000b4000 000aa600 2**2
CONTENTS, ALLOC, LOAD, DATA
7 .rela 0001b468 00000000000b5000 00000000000b5000 000aa800 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
8 .sbat 000000df 00000000000d1000 00000000000d1000 000c5e00 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
This makes it hard to predict the resulting PCR7 as SBAT level is measured there:
- EventNum: 25
PCRIndex: 7
EventType: EV_EFI_VARIABLE_AUTHORITY
DigestCount: 3
Digests:
- AlgorithmId: sha384
Digest: "f143e2948d63fcd3442e841bb36a7e180871f0a8946541961fe9d12e70d0727874600956264dba531e2edd8729c5eb38"
- AlgorithmId: sha256
Digest: "922e939a5565798a5ef12fe09d8b49bf951a8e7f89a0cca7a51636693d41a34d"
- AlgorithmId: sha1
Digest: "15875d39b8872f8aff3a92fc9f9e40ac75268e04"
EventSize: 68
Event:
VariableName: 605dab50-e046-4300-abb6-3dd810dd8b23
UnicodeNameLength: 9
VariableDataLength: 18
UnicodeName: SbatLevel
VariableData: "736261742c312c323032313033303231380a"
Please consider backporting the above mentioned commit or rebasing shim to 15.7+
Comment 1RHEL Program Management
2023-09-16 19:53:33 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 2RHEL Program Management
2023-09-16 19:59:25 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
RHEL currently ships shim-15.6 which doesn't contain commit 0eb07e11b20680200d3ce9c5bc59299121a75388 Author: Chris Coulson <chris.coulson> Date: Tue May 31 22:21:26 2022 +0100 Make SBAT variable payload introspectable and thus doesn't contain '.sbatlevel' PE section: $ objdump -h shimx64.efi shimx64.efi: file format pei-x86-64 Sections: Idx Name Size VMA LMA File off Algn 0 .eh_frame 0001db1c 0000000000005000 0000000000005000 00000400 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 1 .text 0005e663 0000000000023000 0000000000023000 0001e000 2**4 CONTENTS, ALLOC, LOAD, READONLY, CODE 2 .reloc 0000000a 0000000000082000 0000000000082000 0007c800 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 3 .data.ident 00000049 0000000000084000 0000000000084000 0007ca00 2**4 CONTENTS, ALLOC, LOAD, DATA 4 .data 0002d5b4 0000000000085000 0000000000085000 0007cc00 2**4 CONTENTS, ALLOC, LOAD, DATA 5 .vendor_cert 0000037c 00000000000b3000 00000000000b3000 000aa200 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 6 .dynamic 00000100 00000000000b4000 00000000000b4000 000aa600 2**2 CONTENTS, ALLOC, LOAD, DATA 7 .rela 0001b468 00000000000b5000 00000000000b5000 000aa800 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 8 .sbat 000000df 00000000000d1000 00000000000d1000 000c5e00 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA This makes it hard to predict the resulting PCR7 as SBAT level is measured there: - EventNum: 25 PCRIndex: 7 EventType: EV_EFI_VARIABLE_AUTHORITY DigestCount: 3 Digests: - AlgorithmId: sha384 Digest: "f143e2948d63fcd3442e841bb36a7e180871f0a8946541961fe9d12e70d0727874600956264dba531e2edd8729c5eb38" - AlgorithmId: sha256 Digest: "922e939a5565798a5ef12fe09d8b49bf951a8e7f89a0cca7a51636693d41a34d" - AlgorithmId: sha1 Digest: "15875d39b8872f8aff3a92fc9f9e40ac75268e04" EventSize: 68 Event: VariableName: 605dab50-e046-4300-abb6-3dd810dd8b23 UnicodeNameLength: 9 VariableDataLength: 18 UnicodeName: SbatLevel VariableData: "736261742c312c323032313033303231380a" Please consider backporting the above mentioned commit or rebasing shim to 15.7+