Skip to content

ipxe/shim-review

BranchesTags
 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

56 Commits
docs
docs
 
 
examples
examples
 
 
.gitignore
.gitignore
 
 
CODE_OF_CONDUCT.md
CODE_OF_CONDUCT.md
 
 
Dockerfile
Dockerfile
 
 
ISSUE_TEMPLATE.md
ISSUE_TEMPLATE.md
 
 
README.md
README.md
 
 
build.log
build.log
 
 
build.sh
build.sh
 
 
ipxe.der
ipxe.der
 
 
shimaa64.efi
shimaa64.efi
 
 
shimx64.efi
shimx64.efi
 
 

Repository files navigation

What organization or people are asking to have this signed?

This shim review request is coming direct from the iPXE project. The EV code signing certificate is issued by DigiCert and owned by Fen Systems Ltd.

What product or service is this for?

This shim will be used to load iPXE

What's the justification that this really does need to be signed for the whole world to be able to boot it?

Many people have asked over the years for a version of iPXE that can be run with Secure Boot enabled. For example:

Enquiries have also been received from several large companies via the vendor-support@ipxe.org address.

Some OEMs have also reported (in private communication) that the lack of a Secure Boot signed iPXE is one of the reasons driving customers to disable Secure Boot.

Why are you unable to reuse shim from another distro that is already signed?

No distro is currently providing Secure Boot signed versions of iPXE.

Who is the primary contact for security updates, etc.?

The security contacts need to be verified before the shim can be accepted. For subsequent requests, contact verification is only necessary if the security contacts or their PGP keys have changed since the last successful verification.

An authorized reviewer will initiate contact verification by sending each security contact a PGP-encrypted email containing random words. You will be asked to post the contents of these mails in your shim-review issue to prove ownership of the email addresses and PGP keys.

Who is the secondary contact for security updates, etc.?

Were these binaries created from the 15.8 shim release tar?

Please create your shim binaries starting with the 15.8 shim release tar file: https://github.com/rhboot/shim/releases/download/15.8/shim-15.8.tar.bz2

This matches https://github.com/rhboot/shim/releases/tag/15.8 and contains the appropriate gnu-efi source.

Yes, these binaries were created from the 15.8 tag.

URL for a repo that contains the exact code which was built to get this binary:

https://github.com/ipxe/shim/tree/ipxe-15.8

What patches are being applied and why:

Almost all of the above are standard housekeeping patches such as adding the vendor certificate. The one functional change is ipxe: Allow next loader path to be derived from shim path:

ipxe: Allow next loader path to be derived from shim path

Allow loader path to be constructed from the path used to load the
shim itself, e.g.:

    ipxe-shimx64.efi      -> ipxe.efi
    ipxe-shimaa64.efi     -> ipxe.efi
    snponly-shimx64.efi   -> snponly.efi
    snponly-shimaa64.efi  -> snponly.efi

This reduces the complexity of using a signed shim binary to load
iPXE, which (unlike GRUB) has a variety of possible binary names
depending on the requested driver set.  For example, if a site uses
all three of ipxe.efi, intel.efi, and snponly.efi then symlinks can be
used to provide the appropriate shim files:

    # iPXE binaries
    /var/lib/tftpboot/ipxe.efi
    /var/lib/tftpboot/intel.efi
    /var/lib/tftpboot/snponly.efi

    # shim binary (from this repository)
    /var/lib/tftpboot/ipxe-shimx64.efi

    # shim symlinks
    /var/lib/tftpboot/intel-shimx64.efi -> ipxe-shimx64.efi
    /var/lib/tftpboot/snponly-shimx64.efi -> ipxe-shimx64.efi

Do you have the NX bit set in your shim? If so, is your entire boot stack NX-compatible and what testing have you done to ensure such compatibility?

See https://techcommunity.microsoft.com/t5/hardware-dev-center/nx-exception-for-shim-community/ba-p/3976522 for more details on the signing of shim without NX bit.

No, the NX bit is not set.

While it is believed that the shim+iPXE boot stack is NX-compatible (and the iPXE binary is already built with the NX bit set), we do not intend to set the NX bit in the shim until it is set by default in the shim release.

If shim is loading GRUB2 bootloader what exact implementation of Secureboot in GRUB2 do you have? (Either Upstream GRUB2 shim_lock verifier or Downstream RHEL/Fedora/Debian/Canonical-like implementation)

Not applicable: this shim will not be used to load GRUB2.

If shim is loading GRUB2 bootloader and your previously released shim booted a version of GRUB2 affected by any of the CVEs in the July 2020, the March 2021, the June 7th 2022, the November 15th 2022, or 3rd of October 2023 GRUB2 CVE list, have fixes for all these CVEs been applied?

Not applicable: this shim will not be used to load GRUB2.

If shim is loading GRUB2 bootloader, and if these fixes have been applied, is the upstream global SBAT generation in your GRUB2 binary set to 4?

The entry should look similar to: grub,4,Free Software Foundation,grub,GRUB_UPSTREAM_VERSION,https://www.gnu.org/software/grub/

Not applicable: this shim will not be used to load GRUB2.

Were old shims hashes provided to Microsoft for verification and to be added to future DBX updates?

Does your new chain of trust disallow booting old GRUB2 builds affected by the CVEs?

Not applicable: this shim will not be used to load GRUB2.

If your boot chain of trust includes a Linux kernel:

Is upstream commit 1957a85b0032a81e6482ca4aab883643b8dae06e "efi: Restrict efivar_ssdt_load when the kernel is locked down" applied?

Is upstream commit 75b0cea7bf307f362057cc778efe89af4c615354 "ACPI: configfs: Disallow loading ACPI tables when locked down" applied?

Is upstream commit eadb2f47a3ced5c64b23b90fd2a3463f63726066 "lockdown: also lock down previous kgdb use" applied?

Not applicable: this shim will not be used to load a Linux kernel.

Do you build your signed kernel with additional local patches? What do they do?

Not applicable: this shim will not be used to load a Linux kernel.

Do you use an ephemeral key for signing kernel modules?

If not, please describe how you ensure that one kernel build does not load modules built for another kernel.

Not applicable: this shim will not be used to load a Linux kernel.

If you use vendor_db functionality of providing multiple certificates and/or hashes please briefly describe your certificate setup.

If there are allow-listed hashes please provide exact binaries for which hashes are created via file sharing service, available in public with anonymous access for verification.

Not applicable: only a single certificate is used and there are no allow-listed hashes.

If you are re-using a previously used (CA) certificate, you will need to add the hashes of the previous GRUB2 binaries exposed to the CVEs to vendor_dbx in shim in order to prevent GRUB2 from being able to chainload those older GRUB2 binaries. If you are changing to a new (CA) certificate, this does not apply.

Please describe your strategy.

Not applicable: this shim will not be used to load GRUB2.

What OS and toolchain must we use to reproduce this build? Include where to find it, etc. We're going to try to reproduce your build as closely as possible to verify that it's really a build of the source tree you tell us it is, so these need to be fairly thorough. At the very least include the specific versions of gcc, binutils, and gnu-efi which were used, and where to find those binaries.

If the shim binaries can't be reproduced using the provided Dockerfile, please explain why that's the case and what the differences would be.

The Dockerfile provides a reproducible build.

Which files in this repo are the logs for your build?

This should include logs for creating the buildroots, applying patches, doing the build, creating the archives, etc.

The build.log contains the build log.

What changes were made in the distor's secure boot chain since your SHIM was last signed?

For example, signing new kernel's variants, UKI, systemd-boot, new certs, new CA, etc..

Not applicable: this is a new submission.

What is the SHA256 hash of your final SHIM binary?

shimx64.efi 636d581943f1872d4eb17af39b3b7e07ed8dfc5ec5e85779550fa2c01fa3aeae

shimaa64.efi 986978b520a3b159f74da9e16939aac6a986b8467f6f41929e4d94ef87863ad0

How do you manage and protect the keys used in your SHIM?

Key is held in a hardware security module provided by DigiCert.

Do you use EV certificates as embedded certificates in the SHIM?

Yes, the certificate ipxe.der is an EV certificate issued by DigiCert.

Do you add a vendor-specific SBAT entry to the SBAT section in each binary that supports SBAT metadata ( GRUB2, fwupd, fwupdate, systemd-boot, systemd-stub, shim + all child shim binaries )?

Please provide exact SBAT entries for all shim binaries as well as all SBAT binaries that shim will directly boot.

Where your code is only slightly modified from an upstream vendor's, please also preserve their SBAT entries to simplify revocation.

If you are using a downstream implementation of GRUB2 or systemd-boot (e.g. from Fedora or Debian), please preserve the SBAT entry from those distributions and only append your own. More information on how SBAT works can be found here.

Yes.

This shim binary includes the vendor SBAT data:

shim.ipxe,1,iPXE,shim,1,https://github.com/ipxe/shim

This shim will be used to load iPXE, which includes SBAT metadata as of commit f4f9adf61. The current SBAT content in iPXE at the time of writing is:

sbat,1,SBAT Version,sbat,1,https://github.com/rhboot/shim/blob/main/SBAT.md
ipxe,1,iPXE,ipxe.efi,1.21.1+ (g182ee),https://ipxe.org

If shim is loading GRUB2 bootloader, which modules are built into your signed GRUB2 image?

Not applicable: this shim will not be used to load GRUB2.

If you are using systemd-boot on arm64 or riscv, is the fix for unverified Devicetree Blob loading included?

Not applicable: this shim will not be used to load systemd-boot.

What is the origin and full version number of your bootloader (GRUB2 or systemd-boot or other)?

https://github.com/ipxe/ipxe

iPXE currently uses a rolling release model. With a signed shim, this will switch to regular (potentially quarterly) releases.

If your SHIM launches any other components, please provide further details on what is launched.

This shim will be used only to launch iPXE.

If your GRUB2 or systemd-boot launches any other binaries that are not the Linux kernel in SecureBoot mode, please provide further details on what is launched and how it enforces Secureboot lockdown.

Not applicable: this shim will not be used to load GRUB2.

How do the launched components prevent execution of unauthenticated code?

By design, iPXE does not implement any direct binary loaders when running as a UEFI binary. All binary image loading is delegated to the platform's LoadImage() and StartImage() calls. There is therefore no way for iPXE to execute a binary that is not itself already signed for Secure Boot.

Does your SHIM load any loaders that support loading unsigned kernels (e.g. GRUB2)?

No.

What kernel are you using? Which patches does it includes to enforce Secure Boot?

Not applicable: this shim will not be used to load a Linux kernel.

Add any additional information you think we may need to validate this shim.

iPXE has previously been signed directly for Secure Boot and has therefore been subject to several security audits, the results of which have been shared with Microsoft.

Portions of the codebase that are ineligible to be included in Secure Boot signed builds are well understood and documented in the UEFI Signing Requirements document.

Microsoft has commented in its iPXE Security Assurance Review that iPXE's code is of high quality and that its use of the EFI boot services stack is exceptionally well documented.

The most recent security audit carried out for Secure Boot signing found only a single potential bug, which could be exploited only by a malicious PCI device.

This submission was created over a year ago, in February 2023. It has been rebased upon the shim-15.8 release in February 2024.

Given that the Secure Boot team at Microsoft is already well aware of iPXE, we would like to ask the shim-review team to please review only the shim submission aspects (e.g. the correctness of the GPG tags, the reproducibility of the build, the SBAT metadata, and the list of patches), to accept the submission on this basis, and to leave to Microsoft the substantive decision on signing the resulting shim.

About

Reviews of shim

Resources

Readme

Code of conduct

Code of conduct
Activity
Custom properties

Stars

2 stars

Watchers

3 watching

Forks

0 forks
Report repository

Releases

5 tags

Packages

No packages published

Languages

  • Dockerfile 79.2%
  • Shell 20.8%