Morten Linderud
Morten Linderud
Mm, the kernel refuses to read the `MOK` variables unless they are present in the EFI configuration table. So you would need some shim hackery? Am I misunderstanding something? Simply...
Sure, that would be fine I believe. But be aware that it doesn't really do anything on it's own without the shim.
>But that's the idea, no? Provide a MOK store so that the user can give the kernel a trusted key for kernel module signing, while relying on the regular UEFI...
Okay, I didn't bother correcting all the `if err...; err != nil {` stuff in the review :p sorry! Generally looks okay something we should have been doing for a...
Please post complete errors. I'm unable to figure out anything if you keep censoring values for no good reason. I don't know how Void mounts efivarfs, so that is something...
Output of `ls -lah /sys/firmware/efi/efivars/PK-8be4df61-93ca-11d2-aa0d-00e098032b8c /sys/firmware/efi/efivars/KEK-8be4df61-93ca-11d2-aa0d-00e098032b8c /sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f` please
Did you select User Mode in the Secure Boot menu on your thinkpad?
It's refusing to accept the Platform Key so I'm not quite sure what state the secure boot mode should be in for that to be a thing. To me it...
sbctl is developed on a t480s. It should just work. Everything seems in order so this is weird. Never seen this before frankly.
systemd mount efivarfs like this on Arch Linux λ ~ » mount | grep efivar efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) I don't think anything here matters? It did manage...