-
Notifications
You must be signed in to change notification settings - Fork 144
Closed
Labels
acceptedSubmission is ready for sysdevSubmission is ready for sysdevcontacts verified OKContact verification is complete here (or in an earlier submission)Contact verification is complete here (or in an earlier submission)
Description
Confirm the following are included in your repo, checking each box:
- completed README.md file with the necessary information
- shim.efi to be signed
- public portion of your certificate(s) embedded in shim (the file passed to VENDOR_CERT_FILE)
- binaries, for which hashes are added to vendor_db ( if you use vendor_db and have hashes allow-listed )
- any extra patches to shim via your own git tree
- any extra patches to grub via your own git tree or as files
- build logs
- a Dockerfile to reproduce the build of the provided shim EFI binaries
What is the link to your tag in a repo cloned from rhboot/shim-review?
https://github.com/IGEL-Technology/shim-review/tree/IGEL-shim-x64-20240730-1
EDIT: In the meantime, linux kernel diffs, as well as additional sbat sections were requested in the review (see comments below). We included the information in the following tag of the review:
https://github.com/IGEL-Technology/shim-review/releases/tag/IGEL-shim-x64-20240807
What is the SHA256 hash of your final SHIM binary?
90ce33685c5ac241b582bdf27d0ae872b72263a5ae8271ef7f738bd1d13e8e63 shimx64.efi
What is the link to your previous shim review request (if any, otherwise N/A)?
If no security contacts have changed since verification, what is the link to your request, where they've been verified (if any, otherwise N/A)?
N/A
Metadata
Metadata
Assignees
Labels
acceptedSubmission is ready for sysdevSubmission is ready for sysdevcontacts verified OKContact verification is complete here (or in an earlier submission)Contact verification is complete here (or in an earlier submission)