News for hackers. Stuff that matters.
Re:Responsible stewardship of the UEFI Secure Boot ecosystem by AshamedCaptain on Tuesday July 12, 2022 @08:39AM (#32068971)
> Distros don't have to do anything distro-specific to get signed. Most distros use (Microsoft-signed) shim to chainload to something like grub.

You still have to get your own version of shim signed if you want your distro to boot "Scary Boot Prompt"-free. I.e. if you just use RedHat's version of shim, that shim will transparently boot RedHat signed kernels, but refuse to boot SuSE's -- unless you whitelist SuSE's key manually into shim. It's not ideal in any way.

Re:Responsible stewardship of the UEFI Secure Boot ecosystem by Arnavion on Tuesday July 12, 2022 @08:54AM (#32069164)
I believe for OpenSUSE it uses MokManager to get the user to trust the OpenSUSE CA. But it's been a while since I tried it so I might be misremembering. (MokManager is broken on my mobo so I switched to systemd-boot + my own signing keys, which is better for security anyway.)