-
Notifications
You must be signed in to change notification settings - Fork 130
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
Ctrl IQ, Inc EL7 Shim 15.8 for x64 & ia32 #430
Comments
review for ciqliq-shim-EL7-x64-ia32-20240702
|
@dennis-tseng99 Thank you for the review! Can you please elaborate on the following comment?
From what I understand I am building the shim in a centos 7 environment, because the shim is for centos 7. The build log show mock building the shim in a centos 7 environment, correct? Did you see the build the shim being built in a rocky 8.8 env or do you think the shim should be built in a rocky 8.8 environment? Thank you again for the review and I look forward to your clarification. |
@jason-rodri I haven't looked at the review yet, but I think what @dennis-tseng99 means is located here https://github.com/ctrliq/ciq-shim-build/blob/ciqliq-shim-EL7-x64-ia32-20240702/mock-build/ciq_mock_rocky8_static_shim.cfg which what used to build and provide build.log I assume? However, I have some few questions, now that centos7 is EOL:
|
We do plan to maintain and update security patches for centos EL7 including kernel and grub2.
This was an oversight on my part. I did not update the mock-build directory, the files were still from our EL8 submission. The mock-build directory should now be updated with the correct logs
When NX is approved we will attempt to patch the 3.10 kernel to enable NX support. If it is not feasible to add NX support to 3.10 we will sign a ML 6.X kernel which does support the NX feature
We were under the impression that we needed to submit a separate shim request for each EL version we support and could not reuse our EL8 submission for EL7 and EL9. If this is not the case please let us know. Thank you again @dennis-tseng99 and @SherifNagy for the assistance and pointing out my oversight |
The reuse of already signed shim between releases is mainly a vendor choice, personally, I prefer the builds against each release "shim for rocky9 is build on rocky9 and so on ", RHEL, Oracle, Debian, Rocky Linux and others do that, however, I think now ubuntu moved to single shim for all releases and I think fedora do the same since they release twice a year and there might be only one shim release a year for now, it really depends on the vendor's preference / internal polices. Thanks for the clarification, I will look into the submission early next week |
Review of ciqliq-shim-EL7-x64-ia32-20240705
Shim
GRUB2
Kernel
NoteI would be slightly worried to allow running Centos un-patched / unmaintained grub2 and kernels using the Centos's CA via certwrapper, this would make the OS vulnerable even with secureboot enable. LGTM |
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as outdated.
This comment was marked as outdated.
@jason-rodri Can you clarify if you will still include the EoL Centos CA or not? |
We will not be including the EOL centos CA in our EL7 offering. |
review for ciqliq-shim-EL7-x64-ia32-20240702I am not an authorized reviewer, hope this helps anyway
|
Review of ciqliq-shim-EL7-x64-ia32-20240705I am not an authorized reviewer but I want to help
I am not a CentOS user but I assume that both grub and kernel have been hardened to ensure OS security. |
Updated our submission README.md to reflect current stance on certwrapper usage for EL7. |
Considering the worries about arising security issues, the shim community can't possibly track everything on its own and has to trust the organizations to some extent - I'd say that if the worries are so strong about whether this shim should be signed or not, it's up to Microsoft's Hardware Dev Center branch to decide on that, especially considering future shims and the whole chain's NX support. This is also reinforced by how trust gets earned and how easy it can be lost - I doubt that anyone would be willing to risk doing insecure operations here intentionally for a potential reputation loss, i.e.: I myself trust that CIQ Bridge is made secure by design, so that the whole chain remains secure both during the customers' upgrade period and after it, and it's not my responsibility to use it on my own and keep track of everything it does. Things look alright to me and the build does reproduce. Thanks to everyone for the help with reviews! |
Signed binaries returned by MSFT. |
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/ctrliq/ciq-shim-build/tree/ciqliq-shim-EL7-x64-ia32-20240903
What is the SHA256 hash of your final SHIM binary?
SHA256 (shimx64.efi) = 088610925c2491017f6488f6235c6daec4e7f567dfb6c4e8c55d64d6acaafbae
SHA256 (shimia32.efi) = 14822c87e48f9ca65df08a4595ffa8cc6a7564197826521318488178fdf16272
What is the link to your previous shim review request (if any, otherwise N/A)?
Ctrl IQ, Inc Shim 15.8 for x64 & ia32 #366
Ctrl IQ, Inc EL9 Shim 15.8 for x64 #420
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)?
Jason Rodriguez
Michael Young
The text was updated successfully, but these errors were encountered: