Morten Linderud
Morten Linderud
cc @bluecmd :)
It's a bit more complicated. There are also going to be several new certs so you can use different certs for OpROM and Linux distros and so on. This will...
> According to https://github.com/systemd/systemd/pull/29104#pullrequestreview-1613512459, you're supposed to have old and new key installed both now. I missed that memo, can probably take a look at it soon'ish.
@Flickdm Thanks for fixing this :)
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/updating-microsoft-secure-boot-keys/ba-p/4055324 Should implement this soon :)
I don't see anything actionable in this issue. What is the intent with this?
The discussion section has been enabled so I'll just close this issue :)
I realized I don't really know what the `diff*` stuff is about. I'm thinking `mkpkg` and `gitpkg` can be moved to contrib. I think clean-chroots can be moved to devtools...
Ah, this is an oversight because people usually do not pass `--efi-stub` at all I assume. Thanks for looking into it :)
@medhefgo The issue is that `BOOTX64.EFI` is not being booted, and it apparently boots the unsigned sd-boot binary. I found all of this too weird to not have an issue...