Make sure you have provided the following information:
- link to your code branch cloned from rhboot/shim-review in the form user/repo@tag https://github.com/ThinStation/shim-review@ThinStation-shim-x64-20200509
- completed README.md file with the necessary information
- shim.efi to be signed
- public portion of your certificate embedded in shim (the file passed to VENDOR_CERT_FILE)
- 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
Donald A. Cupp Jr.
ThinStation OS Framework for Embedded Systems
https://github.com/rhboot/shim/releases/download/15/shim-15.tar.bz2 15
What's the justification that this really does need to be signed for the whole world to be able to boot it:
I compile a custom kernel, with out-of-tree modules, that is distributed globally to millions of Secure boot enabled systems.
AES256 Hardware Key
No
Grub2: 2.04
https://github.com/Thinstation/thinstation/tree/6.2-Stable/ts/ports/opt/grub2
http://ftp.gnu.org/gnu/grub/grub-2.04.tar.xz
Fedora patches 0001 - 0210
Does not load other components.
GRUB enforces Secure Boot, using the accepted patches (see github.com/rhboot/grub2); fallback.efi and MokManager are shim components that enforce authenticated code already.
No
Linux Kernel 5.4.33: No Patches
N/A Never Signed
d001cbf8128378ac2311bfefca9eaf813b72ab2b7711e99785791d998ffd2d86 shimx64.efi