mirror of
https://git.proxmox.com/git/efi-boot-shim
synced 2025-10-04 18:09:48 +00:00
76c0447e20
This adds support for multiple signatures. It first tries validating the binary by hash, first against our dbx lists, then against our db lists. If it isn't allowed or rejected at that step, it continues to the normal routine of checking all the signatures. At this point it does *not* reject a binary just because a signature is by a cert on a dbx list, though that will override any db list that certificate is listed on. If at any point any assertion about the binary or signature list being well-formed fails, the binary is immediately rejected, though we do allow skipping over signatures which have an unsupported sig->Hdr.wCertificateType. Signed-off-by: Peter Jones <pjones@redhat.com> Upstream: pr#210 |
||
|---|---|---|
| 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.