mirror of
https://git.proxmox.com/git/efi-boot-shim
synced 2025-07-30 21:40:57 +00:00
![]() match_hash() requests the number of keys in a list and it was mistakenly replaced with the size of the Mok node. This would made MokManager to remove the whole Mok node instead of one hash. Signed-off-by: Gary Ching-Pang Lin <glin@suse.com> |
||
---|---|---|
Cryptlib | ||
include | ||
lib | ||
.gitignore | ||
cert.S | ||
COPYRIGHT | ||
crypt_blowfish.c | ||
crypt_blowfish.h | ||
elf_aarch64_efi.lds | ||
elf_arm_efi.lds | ||
elf_ia32_efi.lds | ||
elf_ia64_efi.lds | ||
elf_x86_64_efi.lds | ||
fallback.c | ||
make-certs | ||
Makefile | ||
MokManager.c | ||
MokVars.txt | ||
netboot.c | ||
netboot.h | ||
PasswordCrypt.c | ||
PasswordCrypt.h | ||
README | ||
replacements.c | ||
replacements.h | ||
shim.c | ||
shim.h | ||
testplan.txt | ||
TODO | ||
ucs2.h | ||
version.c.in | ||
version.h |
shim is a trivial EFI application that, when run, attempts to open and execute another application. It will initially attempt to do this via the standard EFI LoadImage() and StartImage() calls. If these fail (because secure boot is enabled and the binary is not signed with an appropriate key, for instance) it will then validate the binary against a built-in certificate. If this succeeds and if the binary or signing key are not blacklisted then shim will relocate and execute the binary. shim will also install a protocol which permits the second-stage bootloader to perform similar binary validation. This protocol has a GUID as described in the shim.h header file and provides a single entry point. On 64-bit systems this entry point expects to be called with SysV ABI rather than MSABI, and so calls to it should not be wrapped. To use shim, simply place a DER-encoded public certificate in a file such as pub.cer and build with "make VENDOR_CERT_FILE=pub.cer".