Secure Boot

[bkw777]

Secure Boot

[bkw777]

Probably not a bad idea.

I have also recently discovered that docker doesn't work on the mainline kernels.

In fact there are all kinds of things that can break under a mainline kernel, like dkms modules failing to build like for virtualbox or displaylink usb monitors, binary modules for video/wifi/etc failing to load or work, etc.

None of these problems are caused by the app, they are problems with the kernel packages, which someone else produces. The place for that kind of info is really on the mainline kernel ppa wiki, and/or kernel.ubuntu.com web site, and/or right in the description in the metadata in the .deb files so it shows up in any package manager.

This is also one of the very reasons I removed all the grub stuff and we don't touch the bootloader files. We install the package, but let the package author, or dpkg, or something else be responsible for breaking someones system from booting.

But, it's probably not a completely unreasonable idea to include maybe a notes/warnings section in the main readme, at least for a short list of major things.

[bkw777]

In the end I'm categorizing this the same way as mainline kernels failing to boot on zfs. #55 #64. It doesn't break anyone's system, the new kernel simply doesn't boot, just like any other new mainline kernel might not boot for countless reasons. The previous kernel is still there, because one thing we do do is decline to uninstall the kernel that's currently running, which means no matter what a new kernel does, you still always have at least the one other runnable kernel installed and bootable. IE: installing a kernel that doesn't boot is not harmful.

[bkw777]

Perhaps this is useful. I have not tried it.
https://github.com/M-P-P-C/Signing-a-Linux-Kernel-for-Secure-Boot

[msangel]

All the instructions are fine untill the drive is not encrypted with luks... Signing kernel with instructions above - ok, Loading cryptsetup - fail.