-
Notifications
You must be signed in to change notification settings - Fork 305
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
lib/bootloader-zipl: Check for Secure Boot before zipl #3080
Conversation
Hi @nikita-dubrovskii. Thanks for your PR. I'm waiting for a ostreedev member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
78e1fbd
to
305ee04
Compare
Here is a how-to: coreos/enhancements#10 |
305ee04
to
18dd377
Compare
return glnx_prefix_error (error, "spawning dmesg"); | ||
if (!g_spawn_check_exit_status (status, error)) | ||
return glnx_prefix_error (error, "`dmesg` failed"); | ||
*out_enabled = (output != NULL && strstr (output, "Secure-IPL enabled") != NULL); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feels weird to be grepping for strings in logs for something like Secure Boot. I think --kernel
prevents a simple e.g. echo Secure-IPL enabled > /dev/kmsg
from throwing this off, but my vote would be to stick with the sysfs flag and open a issue against RHEL 9 to have it backported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dropped dmesg
and now read kmsg
directly. I don't know when kernel fix comes, so it'd be better to have this workaround until former happens.
18dd377
to
274eb2c
Compare
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks sane, just some minor nits.
274eb2c
to
c3a9a64
Compare
One thing I don't quite understand btw...isn't zipl in the position to check for secure boot itself? Would it make more sense for the code here to always run |
New versions are able to detect it (when |
Followup fixes in #3119 - can you review? |
Starting with z/VM Version 7 Release 3.0, service level 2301 we can run Linux with Secure Boot enabled