NewStartOS V4 shim-15.6 x64 and ia32

[LiangJianNSDL]

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 or as files
• 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/LiangJianNSDL/shim-review/tree/nsdl-v4-shim-amd64-i386-20221028

---

What is the SHA256 hash of your final SHIM binary?

---

sha256sum shimia32.efi
fa07390322fd0c3b913a2ea58f98e6e584b8d871025664327a9b7cfbd4cb7643 shimia32.efi
sha256sum shimx64.efi
841a5a2d59a91b2e4fc6e2a9309cd2240833f08b9aad417cbba62f1aaf909fd2 shimx64.efi

---

What is the link to your previous shim review request (if any, otherwise N/A)?

---

N/A

[frozencemetery]

SBAT is either incorrect or you're missing multiple security updates to your grub2.

[LiangJianNSDL]

SBAT is either incorrect or you're missing multiple security updates to your grub2.

Thanks, I have fixed SBAT for my shim and grub2 and updated these files, you can check it again.
If there something need to fix , please contact us. Thanks your effort.

[dennis-tseng99]

The hash value seems to not match with the above values:
What is the SHA256 hash of your final SHIM binary?

sha256sum shimia32.efi

89ea4fe5c9bd0ad07bdec54c355290b28b2fcb69745d8d10dc0b39e8aaf72dc3 shimia32.efi

sha256sum shimx64.efi

1e578f73ab4b253e030d66e9545b7faceb7b3f76319803f7e1330bebb1e6f08a shimx64.efi

[LiangJianNSDL]

Thanks for your reply. I rerun dockerfile file, sha256sum shimia32.efi and shimx64.efi are the same as below. Please see attached dockerfile log. You can find the newest dockerfile at #303 <#303 > sha256sum shimia32.efi 89ea4fe5c9bd0ad07bdec54c355290b28b2fcb69745d8d10dc0b39e8aaf72dc3 shimia32.efi sha256sum shimx64.efi 1e578f73ab4b253e030d66e9545b7faceb7b3f76319803f7e1330bebb1e6f08a shimx64.efi 热爱生活 用心工作 您的问题是我的需求 敢为人先 成事为乐 ❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉ 广东中兴新支点技术有限公司 广东省LINUX公共服务技术支持中心 OS产品部 梁健 手 机：15918722194 邮 ***@***.*** 地 址：广州市黄埔区伴河路190号建科广场A栋10层 P.C.510663 网 址：http://www.gd-linux.com ❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉❉ ------------------------------------------------------------------ 发件人：Dennis Tseng ***@***.***> 发送时间：2022年12月26日(星期一) 23:22 收件人：rhboot/shim-review ***@***.***> 抄　送：梁健 ***@***.***>; Author ***@***.***> 主　题：Re: [rhboot/shim-review] NewStartOS V4 shim-15.6 x64 and ia32 (Issue #289) The hash value seems to not match with the above values: sha256sum shimia32.efi 89ea4fe5c9bd0ad07bdec54c355290b28b2fcb69745d8d10dc0b39e8aaf72dc3 shimia32.efi sha256sum shimx64.efi 1e578f73ab4b253e030d66e9545b7faceb7b3f76319803f7e1330bebb1e6f08a shimx64.efi — Reply to this email directly, view it on GitHub <#289 (comment) >, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYTCHF3JQJBZTTJOPGWWRDTWPGZ2JANCNFSM6AAAAAARQ2W3NY >. You are receiving this because you authored the thread.Message ID: ***@***.***> sha256sum shimia32.efi 89ea4fe5c9bd0ad07bdec54c355290b28b2fcb69745d8d10dc0b39e8aaf72dc3 shimia32.efi sha256sum shimx64.efi 1e578f73ab4b253e030d66e9545b7faceb7b3f76319803f7e1330bebb1e6f08a shimx64.efi sha256sum shimia32.efi 89ea4fe5c9bd0ad07bdec54c355290b28b2fcb69745d8d10dc0b39e8aaf72dc3 shimia32.efi sha256sum shimx64.efi 1e578f73ab4b253e030d66e9545b7faceb7b3f76319803f7e1330bebb1e6f08a shimx64.efi NewStartOS V4 shim-15.6 x64 and ia32 #303

[dennis-tseng99]

Thank LiangJianNSDL. Yes, I saw your hash is correct after you re-run Dockerfile. Therefore, I just guess the hash values you mentioned in this page must be a typo.

What is the SHA256 hash of your final SHIM binary?

sha256sum shimia32.efi fa07390322fd0c3b913a2ea58f98e6e584b8d871025664327a9b7cfbd4cb7643 shimia32.efi sha256sum shimx64.efi 841a5a2d59a91b2e4fc6e2a9309cd2240833f08b9aad417cbba62f1aaf909fd2 shimx64.efi

[LiangJianNSDL]

Thank LiangJianNSDL. Yes, I saw your hash is correct after you re-run Dockerfile. Therefore, I just guess the hash values you mentioned in this page must be a typo.

What is the SHA256 hash of your final SHIM binary?

sha256sum shimia32.efi fa07390322fd0c3b913a2ea58f98e6e584b8d871025664327a9b7cfbd4cb7643 shimia32.efi sha256sum shimx64.efi 841a5a2d59a91b2e4fc6e2a9309cd2240833f08b9aad417cbba62f1aaf909fd2 shimx64.efi

Thanks, the SHA256 hash of my final SHIM binary is as follows:
sha256sum shimia32.efi
89ea4fe5c9bd0ad07bdec54c355290b28b2fcb69745d8d10dc0b39e8aaf72dc3 shimia32.efi
sha256sum shimx64.efi
1e578f73ab4b253e030d66e9545b7faceb7b3f76319803f7e1330bebb1e6f08a shimx64.efi

You can find it in the #303
If there something need to fix , please contact us. Thanks your effort.

[frozencemetery]

Please note #307 .

[steve-mcintyre]

Superseded by #303