shim 15.8 for MIRACLE LINUX 9

[tSU-RooT]

Confirm the following are included in your repo, checking each box:

• completed README.md file with the necessary information
• shim.efi to be signed
• public portion of your certificate(s) embedded in shim (the file passed to VENDOR_CERT_FILE)
• binaries, for which hashes are added to vendor_db ( if you use vendor_db and have hashes allow-listed )
• any extra patches to shim via your own git tree or as files
• any extra patches to grub via your own git tree or as files
• build logs
• a Dockerfile to reproduce the build of the provided shim EFI binaries

---

What is the link to your tag in a repo cloned from rhboot/shim-review?

---

https://github.com/miraclelinux/shim-review/tree/miraclelinux-x64-20240524

---

What is the SHA256 hash of your final SHIM binary?

---

60485ece0fa7d8a01975e65d6845b9c084018e4c15d40e2d2d1bbe0bbbdca5d9 shimx64.efi

---

What is the link to your previous shim review request (if any, otherwise N/A)?

---

#264 is previous shim-review request (accepted)

---

If no security contacts have changed since verification, what is the link to your request, where they've been verified (if any, otherwise N/A)?

---

Security contacts are changed, Primary contact is updated to my colleague.
Second contact is me(verified).
#266 (comment)

[steve-mcintyre]

@tSU-RooT has had contact verification done before (hi!)
Sending a message to Masayuki Moriyama now...

[moriyama]

I received the following words:

Chaldean darkening alienation defenses ea keybinding Skye cupid skillful co=
llectivism

[aronowski]

Seems OK to me. I'll submit the appropriate UKI/systemd-boot SBAT entries to this issue.

Just one positive review (might be from a non-accredited reviewer) remaining and the application can be accepted.

[akodanev]

Shim review of "miraclelinux-x64-20240524" (by a non-accredited reviewer):

1. Now includes one more certificate, valid until 2029.
2. There are no additional patches for the 15.8 release.
3. NX bit is not set.
4. The grub policy is set to `grub,3' (NTFS module not included)
5. .sbat section: why is shim.miracle now set to 2?

sbat,1,SBAT Version,sbat,1,https://github.com/rhboot/shim/blob/main/SBAT.md
shim,4,UEFI shim,shim,1,https://github.com/rhboot/shim
shim.miracle,2,Cybertrust Japan,shim,15.8,[email protected]

6. Reproducible build:

#25 [21/21] RUN sha256sum /usr/share/shim/15.8-2.el9.ML.1/x64/shimx64.efi /shimx64.efi
#25 0.283 60485ece0fa7d8a01975e65d6845b9c084018e4c15d40e2d2d1bbe0bbbdca5d9  /usr/share/shim/15.8-2.el9.ML.1/x64/shimx64.efi
#25 0.289 60485ece0fa7d8a01975e65d6845b9c084018e4c15d40e2d2d1bbe0bbbdca5d9  /shimx64.efi
#25 DONE 0.3s

GRUB, Linux kernel

Based on RHEL9.

---

So there is a question about the generation number bump of shim.miracle, otherwise the rest looks good to me.

Also minor comments about SBAT sections consistency:

• The last part of the component name changes for UKI, for all other entries it is .miracle. Just out of curiosity, is there a reason for this?
• Some vendor_url entries with [email protected] address have mail:, mailto: prefixes or nothing.

[steve-mcintyre]

Review of shim 15.8 for MIRACLE LINUX 9

Good

General

• Contact verification completed - OK
• key management using an HSM: Yubikey - OK
• Switched to a new embedded cert for a new root of trust - OK

Shim

• Builds from 15.8 upstream (ish - see issues below), with no
  patches - OK
• shim builds reproduce here for x64 and ia32 with the Dockerfile - OK

60485ece0fa7d8a01975e65d6845b9c084018e4c15d40e2d2d1bbe0bbbdca5d9  /usr/share/shim/15.8-2.el9.ML.1/x64/shimx64.efi
60485ece0fa7d8a01975e65d6845b9c084018e4c15d40e2d2d1bbe0bbbdca5d9  /shimx64.efi

• NX bit not set on shim binaries - OK

Issues / queries

• I don't see why you're grabbing Peter's
  shim-unsigned-x64-15.8-2.el9.src.rpm rather than just using the
  upstream shim tarball directly. This isn't a blocker for this review
  as it's possible to check the tarball checksum from the
  src.rpm. Please don't do this again, though.
• You say "We don't use vendor_db functionality in this build." but
  you quite clearly do. From the build:

make TOPDIR=.. -f ../Makefile COMMIT_ID=5914984a1ffeab841f482c791426d7ca9935a5e6 EFIDIR=almalinux PKGNAME=shim RELEASE=2.el9.ML.1 ENABLE_SHIM_HASH=true SBAT_AUTOMATIC_DATE=2023012900 VENDOR_DB_FILE=/builddir/build/SOURCES/vendordb.esl 'DEFAULT_LOADER=\\\\grubx64.efi' all

I can see three .der files in your submission, and maybe those
three keys in your vendordb.esl. As requested in the README.ms
template: "If you use vendor_db functionality of providing multiple
certificates and/or hashes please briefly describe your certificate
setup."

I'm stopping here until this is resolved.

[moriyama]

I can see three .der files in your submission, and maybe those
three keys in your vendordb.esl. As requested in the README.ms
template: "If you use vendor_db functionality of providing multiple
certificates and/or hashes please briefly describe your certificate
setup."

Thanks for your review.

2 certificates enrolled in vendor_db.
vendor_db contains ml9secureboot001.der and ml9secureboot002.der, which are included in this repository.