diff options
| author | Matthew Garrett <mjg@redhat.com> | 2012-07-28 00:42:43 -0400 |
|---|---|---|
| committer | Matthew Garrett <mjg@redhat.com> | 2012-07-28 00:42:43 -0400 |
| commit | ffc0e2424ba402907ca20906cc26aa20f12984cb (patch) | |
| tree | 0ec3924871c45ea16b10e5ff536e21b7a77af7c9 | |
| parent | 00ced0c1259b400ef135e9415d917f908e9a4500 (diff) | |
| download | efi-boot-shim-ffc0e2424ba402907ca20906cc26aa20f12984cb.tar.gz efi-boot-shim-ffc0e2424ba402907ca20906cc26aa20f12984cb.zip | |
Add basic documentation
| -rw-r--r-- | README | 16 |
1 files changed, 16 insertions, 0 deletions
@@ -0,0 +1,16 @@ +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.
\ No newline at end of file |
