UEFI shim loader
C C++ Other
#1 Compare This branch is 45 commits behind rhinstaller:master.
Latest commit e22a7b5 Sep 17, 2015 @lcrosetto lcrosetto committed with vathpela Fix recursive reference for RELEASE
Building 0.9 with GNU Make 4.0 fails with the following error:

Makefile:4: *** Recursive variable 'RELEASE' references itself (eventually).  Stop.

Change RELEASE to simply-expanded.

Signed-off-by: Linn Crosetto <linn@hpe.com>
Permalink
Failed to load latest commit information.
Cryptlib
include
lib
.gitignore
COPYRIGHT
Makefile
MokManager.c MokManager: Nerf SHA-1 again for actual hashes and signatures. Jun 16, 2015
MokVars.txt
PasswordCrypt.c additional bounds-checking on section sizes Apr 11, 2014
PasswordCrypt.h MokManager: support Tradition DES hash Sep 26, 2013
README Replace build instructions in README with something not completely wr… Jul 21, 2014
TODO
cert.S
crypt_blowfish.c MokManager: support blowfish-based crypt() hash Sep 26, 2013
crypt_blowfish.h
elf_aarch64_efi.lds Make sure our build-id notes wind up at a reasonable place. Jun 30, 2015
elf_arm_efi.lds Make sure our build-id notes wind up at a reasonable place. Jun 30, 2015
elf_ia32_efi.lds
elf_ia64_efi.lds Make sure our build-id notes wind up at a reasonable place. Jun 30, 2015
elf_x86_64_efi.lds Make sure our build-id notes wind up at a reasonable place. Jun 30, 2015
fallback.c
make-certs
netboot.c
netboot.h
replacements.c Ensure that apps launched by shim get correct BS->Exit() behavior Jun 11, 2015
replacements.h Ensure that apps launched by shim get correct BS->Exit() behavior Jun 11, 2015
shim.c
shim.h
testplan.txt
ucs2.h
version.c.in Add ident-like blobs to shim.efi for version checking. Oct 3, 2013
version.h

README

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".