├── .gitignore ├── ISSUE_TEMPLATE.md └── README.md /.gitignore: -------------------------------------------------------------------------------- 1 | .*.sw? 2 | *~ 3 | -------------------------------------------------------------------------------- /ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | Make sure you have provided the following information: 2 | 3 | - [ ] link to your code branch cloned from rhboot/shim-review in the form user/repo@tag 4 | - [ ] completed README.md file with the necessary information 5 | - [ ] shim.efi to be signed 6 | - [ ] public portion of your certificate embedded in shim (the file passed to VENDOR_CERT_FILE) 7 | - [ ] any extra patches to shim via your own git tree or as files 8 | - [ ] any extra patches to grub via your own git tree or as files 9 | - [ ] build logs 10 | 11 | 12 | ###### What organization or people are asking to have this signed: 13 | `[your text here]` 14 | 15 | ###### What product or service is this for: 16 | `[your text here]` 17 | 18 | ###### What is the origin and full version number of your shim? 19 | `[your text here]` 20 | 21 | ###### What's the justification that this really does need to be signed for the whole world to be able to boot it: 22 | `[your text here]` 23 | 24 | ###### How do you manage and protect the keys used in your SHIM? 25 | `[your text here]` 26 | 27 | ###### Do you use EV certificates as embedded certificates in the SHIM? 28 | `[your text here]` 29 | 30 | ###### What is the origin and full version number of your bootloader (GRUB or other)? 31 | `[your text here]` 32 | 33 | ###### If your SHIM launchers any other components, please provide further details on what is launched 34 | `[your text here]` 35 | 36 | ###### How do the launched components prevent execution of unauthenticated code? 37 | `[your text here]` 38 | 39 | ###### Does your SHIM load any loaders that support loading unsigned kernels (e.g. GRUB)? 40 | `[your text here]` 41 | 42 | ###### What kernel are you using? Which patches does it includes to enforce Secure Boot? 43 | `[your text here]` 44 | 45 | ###### What changes were made since your SHIM was last signed? 46 | `[your text here]` 47 | 48 | ###### What is the hash of your final SHIM binary? 49 | `[your text here]` 50 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | This repo is for review of requests for signing shim. To create a request for review: 2 | 3 | - clone this repo 4 | - edit the template below 5 | - add the shim.efi to be signed 6 | - add build logs 7 | - commit all of that 8 | - tag it with a tag of the form "myorg-shim-arch-YYYYMMDD" 9 | - push that to github 10 | - file an issue at https://github.com/rhboot/shim-review/issues with a link to your branch 11 | 12 | Note that we really only have experience with using grub2 on Linux, so asking 13 | us to endorse anything else for signing is going to require some convincing on 14 | your part. 15 | 16 | Here's the template: 17 | 18 | ------------------------------------------------------------------------------- 19 | What organization or people are asking to have this signed: 20 | ------------------------------------------------------------------------------- 21 | [your text here] 22 | 23 | ------------------------------------------------------------------------------- 24 | What product or service is this for: 25 | ------------------------------------------------------------------------------- 26 | [your text here] 27 | 28 | ------------------------------------------------------------------------------- 29 | What's the justification that this really does need to be signed for the whole world to be able to boot it: 30 | ------------------------------------------------------------------------------- 31 | [your text here] 32 | 33 | ------------------------------------------------------------------------------- 34 | Who is the primary contact for security updates, etc. 35 | ------------------------------------------------------------------------------- 36 | - Name: 37 | - Position: 38 | - Email address: 39 | - PGP key, signed by the other security contacts, and preferably also with signatures that are reasonably well known in the linux community: 40 | 41 | ------------------------------------------------------------------------------- 42 | Who is the secondary contact for security updates, etc. 43 | ------------------------------------------------------------------------------- 44 | - Name: 45 | - Position: 46 | - Email address: 47 | - PGP key, signed by the other security contacts, and preferably also with signatures that are reasonably well known in the linux community: 48 | 49 | ------------------------------------------------------------------------------- 50 | What upstream shim tag is this starting from: 51 | ------------------------------------------------------------------------------- 52 | [our url here] 53 | 54 | ------------------------------------------------------------------------------- 55 | URL for a repo that contains the exact code which was built to get this binary: 56 | ------------------------------------------------------------------------------- 57 | [your url here] 58 | 59 | ------------------------------------------------------------------------------- 60 | What patches are being applied and why: 61 | ------------------------------------------------------------------------------- 62 | [your text here] 63 | 64 | ------------------------------------------------------------------------------- 65 | What OS and toolchain must we use to reproduce this build? Include where to find it, etc. We're going to try to reproduce your build as close as possible to verify that it's really a build of the source tree you tell us it is, so these need to be fairly thorough. At the very least include the specific versions of gcc, binutils, and gnu-efi which were used, and where to find those binaries. 66 | ------------------------------------------------------------------------------- 67 | [your text here] 68 | 69 | ------------------------------------------------------------------------------- 70 | Which files in this repo are the logs for your build? This should include logs for creating the buildroots, applying patches, doing the build, creating the archives, etc. 71 | ------------------------------------------------------------------------------- 72 | [your text here] 73 | 74 | ------------------------------------------------------------------------------- 75 | Add any additional information you think we may need to validate this shim 76 | ------------------------------------------------------------------------------- 77 | [your text here] 78 | --------------------------------------------------------------------------------