mirror of
https://git.proxmox.com/git/efi-boot-shim
synced 2025-08-04 23:26:30 +00:00
![]() When shim is invoked from a relative path (e.g: from the UEFI shell), the Loaded Image handle LoadOptions can be set to the binary relative path. But the is_our_path() function only checks if LoadOptions is set to the absolute path of shim to ignore it. So if a relative path is there, shim would set itself as the secondary loader and invoke itself in a loop. To prevent that, use the path in LoadOptions to calculate the absolute path and compare it with the one in the Loader Image handle FilePath. Resolves: bz#1622485 Signed-off-by: Javier Martinez Canillas <javierm@redhat.com> Reviewed-by: Maran Wilson maran.wilson@oracle.com Tested-by: Maran Wilson maran.wilson@oracle.com Upstream-commit-id: e563bc3dcd1 |
||
---|---|---|
Cryptlib | ||
include | ||
lib | ||
.gitignore | ||
.syntastic_c_config | ||
.travis.yml | ||
buildid.c | ||
BUILDING | ||
cert.S | ||
COPYRIGHT | ||
crypt_blowfish.c | ||
elf_aarch64_efi.lds | ||
elf_arm_efi.lds | ||
elf_ia32_efi.lds | ||
elf_ia64_efi.lds | ||
elf_x86_64_efi.lds | ||
errlog.c | ||
fallback.c | ||
httpboot.c | ||
make-certs | ||
Make.coverity | ||
Make.defaults | ||
Make.rules | ||
Make.scan-build | ||
Makefile | ||
model.c | ||
mok.c | ||
MokManager.c | ||
MokVars.txt | ||
netboot.c | ||
PasswordCrypt.c | ||
README | ||
README.fallback | ||
README.tpm | ||
replacements.c | ||
shim.c | ||
shim.h | ||
testplan.txt | ||
TODO | ||
tpm.c | ||
travis-build.sh | ||
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. On systems with a TPM chip enabled and supported by the system firmware, shim will extend various PCRs with the digests of the targets it is loading. A full list is in the file README.tpm . 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". There are a couple of build options, and a couple of ways to customize the build, described in BUILDING.