Skip to content
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

Secure boot variable seems not consistent between varstored and VM #20

Open
gthvn1 opened this issue Sep 6, 2023 · 0 comments
Open

Comments

@gthvn1
Copy link

gthvn1 commented Sep 6, 2023

Hello,

When I start a VM with secure boot enabled it looks like the UEFI variable is not consistent between what is seen with varstore-get and the sysfs of the VM. From the host I see that variable is equal to 0:

[17:39 xcp-ng-fwkum ~]# varstore-get 27d6e5cb-8c50-c34b-b094-43271bfcc0d2 8be4df61-93ca-11d2-aa0d-00e098032b8c SecureBoot |hexdump -C
00000000  00                                                |.|

While in the VM I see it set to 1:

root@ci-debian-12-uefi:~# dmesg |grep secure
[    0.000000] secureboot: Secure boot enabled
root@ci-debian-12-uefi:~# cat /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c | hexdump -C
00000000  06 00 00 00 01                                    |.....|

Can we rely on varstore-get to know if secure boot is enabled in the VM?

@gthvn1 gthvn1 changed the title Secure boot variables seems not consistent between varstored and VM Secure boot variable seems not consistent between varstored and VM Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant