mirror of
https://git.proxmox.com/git/efi-boot-shim
synced 2025-08-13 13:32:48 +00:00
5e3d9cd998
There's clearly not enough conformance to a single coding style here. To some extent that can't really change - I don't intend to adopt edk2's style for the main codebase, but re-formatting the code we borrow from edk2 would be insane. This commit adds a .clang-format file, to be used on new files as such: clang-format --style=file -i foo.c It can also be used when new free-standing code is added to existing files, using the clang-format --lines= option. The starting style in this is pretty close to the Linux kernel style, with a couple of minor modifications. Signed-off-by: Peter Jones <pjones@redhat.com> |
||
|---|---|---|
| .github/workflows | ||
| Cryptlib | ||
| include | ||
| lib | ||
| .clang-format | ||
| .gitignore | ||
| .syntastic_c_config | ||
| 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.