-
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.8 - shimx64.efi and shimia32.efi for OpenText(MicroFocus) ZENworks #389
Comments
Hi, I'm not an authorized reviewer, but I'd like to contribute and help Build reproducibilityBuild is NOT reproducible:
|
Thanks for review. sha256sum: |
I'm not an authorized reviewer, but I'd like to contribute and help Review of OpenText(MicroFocus) ZENworksBuild reproducibility
Shim
Certificate
So, does your new chain of trust disallow booting old GRUB2 builds affected by the CVEs? GRUB
Custom EFI binary
Kernel
|
Build reproduces, checksums match, characteristics seem alright. The lack of commit eadb2f47a3ced5c64b23b90fd2a3463f63726066 "lockdown: also lock down previous kgdb use" has been justified - debugging is not enabled. The lack of ephemeral keys has been justified due to it being discussed as part of review #393, which got accepted. Questions: The SBAT entries still reference MicroFocus, despite the fact that I can see the name changed as part of this application and the company website. Should the entries be preserved, or do you prefer to update them due to the name change? If the latter, ping me and I'll re-review the parts that changed ASAP. Notes: I am a bit worried about the current GRUB2 module list the same way as during the last review, but the same one got approved, so I guess we can leave it as-is. |
We thought of maintaining the sbat only with version changes, Kindly let me know is it mandatory to update or else i can do it next submission. |
On 2024.04.15 22:47:35, MuthuvelKuppusamy wrote:
We thought of maintaining the sbat only with version changes, Kindly let me know is it mandatory to update or else i can do it next submission.
I myself don't mind it staying the way it is now especially if it's about some
compatibility-related scenarios. I'm just suggesting that if you do want to
change the entries, you can do so now and have the updated application
re-reviewed fairly quickly.
I'm speaking on behalf of myself only. I don't know what Microsoft will think
about this - it's up to you to make the decision.
… --
Reply to this email directly or view it on GitHub:
#389 (comment)
You are receiving this because you were assigned.
Message ID: ***@***.***>
|
Thanks for the review. Please find the new changes in place, and sbat section details as below.objdump -s -j .sbat shimx64.efi shimia32.efishimx64.efi: file format pei-x86-64 Contents of section .sbat: shimia32.efi: file format pei-i386 Contents of section .sbat: |
On 2024.04.16 05:43:12, MuthuvelKuppusamy wrote:
Thanks for the review.
Please find the new changes in place, and sbat section details as below.
[...]
----
Looks OK. Incorporate the change to the application, tag it appropriately, push
the changes, update the tag in the Github issue's original post and I'll take
another look at the application.
… --
Reply to this email directly or view it on GitHub:
#389 (comment)
You are receiving this because you were assigned.
Message ID: ***@***.***>
|
Thanks for the review. I have created the tag with latest changes https://github.com/MuthuvelKuppusamy/shim-review/releases/tag/opentext-shim-x64-ia32-20240417 and updated the same in issues template. |
Awesome! Accepting it! |
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/MuthuvelKuppusamy/shim-review/releases/tag/opentext-shim-x64-ia32-20240417
What is the SHA256 hash of your final SHIM binary?
98f0017ba0040e495726953e82a61ad3de09ba5294c105c5a5e260363422dd85 shimx64.efi
b8f98e7f4a8c3d534def16bdfc13b6b605177ed9279936fd0d5453520e8657e2 shimia32.efi
What is the link to your previous shim review request (if any, otherwise N/A)?
#320
The text was updated successfully, but these errors were encountered: