-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shim-15.6 for Isoo (2022-08-02) #246
Comments
My previously accepted SHIM: |
Disclaimer: I am not an authorized reviewer Hi, I have checked below points.
Each packages are latest version of debian bullseye.
Serial number: Surely, switched to new certificate.
Looks ok to me: Storing private key in HSM and restriction for usable only while production build.
I think OK.
I have reviewed source of 2.06-2ubuntu7, I found not fixed vulnerability of June 7th 2022 grub2 CVE list. For a sample, CVE-2021-3695 fix "Drop greyscale support" is not patched on Ubuntu 22.04. Maybe to wait for ubuntu's new release is reasonable. |
This is very concerning, stating that the issues are fixed but then using Ubuntu's grub which does not have the bug fixes yet due to complex process issues. You want to make sure you have not signed any of the existing grubs with the key trusted in this shim, wait for a new grub to be made available on the Ubuntu side, and then update the submission. |
@julian-klode @tSU-RooT https://github.com/haobinnan/shim-review/tree/isoo-shim-20220802 |
Quick skim here:
You're good to go here. |
Thank you very much for your quick response and review! |
Steve you scared me for a bit because you wrote 2.06-2 :D |
Confirm the following are included in your repo, checking each box:
What is the link to your tag in a repo cloned from rhboot/shim-review?
https://github.com/haobinnan/shim-review/tree/isoo-shim-20220802
What is the SHA256 hash of your final SHIM binary?
shimia32.efi.sha256sum: 5306c91274b4678e6ad76345904064a61cf4c79fa389b7e0a101904600ada68d
shimx64.efi.sha256sum: 787e59f2c49e0a7e0ab2f3748c4213b98e2445f2500b0bed4f158d9d3468ef62
The text was updated successfully, but these errors were encountered: