Custom PXE Centos 7 Secureboot MOK is not validated
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 348
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am trying to get shim working with PXE by building it myself and inserting the key during the build process. However my MOK is never used in checking subsequent boot components such as grub or the kernel. Secureboot is on and the DB keys are used to validate grub and the kernel. I checked this by removing the keys with sbsigntools, whilst trying to load grub it gave me an error, as is correct. Then for testing I tried to remove the MOK key signature from grub and the kernel and shim allowed booting. My build process is as follows:
make clean
cp ${MOK_KEY_LOC} ./pub.cer
make VENDOR_CERT_FILE=pub.cer
make ENABLE_SBSIGN=1 TOPDIR=. EFIDIR=. DESTDIR=/var/lib/tftpboot \
DEFAULT_LOADER=\\\\grubx64.efi install
I tried many varients of the last line basically trying all variables outlined in the BUILDING file.
I'm using the shim-15 release and grub-2.02-90.
Thanks in advance
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read BUILDING and reproduce the shim-15 build and install commands shown, using the custom pub.cer and PXE destination. Compare the resulting MOK handling with validation of grub-2.02-90 and the kernel; done means the custom MOK is used to validate subsequent boot components while Secure Boot remains enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, centos
- Domain
- build-system, operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100