Go to file
Peter Jones 8807e36aae [fallback] Try to execute the first new boot option.
I'm told rebooting is sometimes unreliable when called here, and we'll
get bootx64.efi loaded anyway.  I'll just assume that's true and try to
load the first option, since it's clearly what we'd prefer happens next.

Signed-off-by: Peter Jones <pjones@redhat.com>
2013-05-02 14:58:44 -04:00
Cryptlib Remove temp file checked in by accident 2012-07-09 10:38:30 -04:00
cert.S Fix data alignment on vendor_cert so we don't wind up with padding. 2012-09-06 16:43:30 -04:00
COPYRIGHT Add copyright file 2012-07-09 11:03:12 -04:00
dbx.S Initialize the size of vendor dbx as 0 2012-10-30 10:35:36 -04:00
fallback.c [fallback] Try to execute the first new boot option. 2013-05-02 14:58:44 -04:00
make-certs Sign MokManager with a locally-generated key 2012-11-26 13:43:50 -05:00
Makefile Add a fallback loader for when shim is invoked as BOOTX64.EFI 2013-04-30 09:46:22 -04:00
MokManager.c Make sure the menu shows when the callback fails 2013-01-03 12:20:30 +08:00
MokVars.txt Add documentation of the Mok variables 2012-10-30 16:14:02 -04:00
netboot.c Don't fail if there's no network devices 2012-11-01 16:03:24 -04:00
netboot.h Add draft version of Neil's netboot code 2012-10-12 20:14:14 -04:00
PeImage.h dos2unix PeImage.h 2012-09-06 12:01:43 -04:00
README Add basic documentation 2012-07-28 00:42:43 -04:00
shim.c Make shim use fallback when appropriate. 2013-04-30 09:46:22 -04:00
shim.h Switch to using db format for MokList and MokNew 2012-10-12 19:55:20 -04:00
signature.h Switch to using db format for MokList and MokNew 2012-10-12 19:55:20 -04:00
TODO Update TODO 2012-07-09 10:39:14 -04:00
ucs2.h Add StrCSpn() 2013-04-30 09:46:22 -04:00

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 hex dump of the public certificate in cert.h
and build it with make.