Enabling Secure Boot in MX Linux

[asqwerth]

It may not be 100% Arch grub, according to the first post in that thread. Still has some minimal patching, apparently.

[Head_on_a_Stick]

that would be another thread

Yes, sorry. Probably nothing to worry about though — in the unlikely event that any Archers try to dual-boot with MX I'm sure they will be able to figure it out for themselves.

[fehlix]

OK, I just tested with having a Manjaro's vanilla grub installed. The intel-µcode line in the generated grub.cfg get nicely generated from normal installed MX Linux and also with the secure-boot enabled MX-Linux (with having applied the receipt from post #1 and the os_prober corrections mentioned in my post above ( EDIT: and now also in post #1). I'm currently don't have another arch-based system to further investigate the mentioned µcode-issue in the grub-entries for arch-systems.

[oops]

Now that Debian buster fully supports Secure Boot it is possible to also enable MX-19. Unfortunately Secure Boot does not allow for custom kernel modules so this guide should not be followed if the proprietary NVIDIA, Broadcom or VirtualBox drivers are needed, it also removes the ability to load ndiswrapper-derived drivers.
...

Thanks for the tuto.
Good news for the secure boot ... but bad new for me for one machine, I use VirtualBox.