limine VS Super-UEFIinSecureBoot-Disk

I assume this person meant to say `Limine'.

It's what I use for dualbooting Windows and Linux. It's really easy to Install, Use & Understand.

https://limine-bootloader.org/

They also publish a PHILOSOPHY.md page in their MS-source-git (github) that is, which is clearly offensive to us and many linux users:

I'm using Limine for bootloader, and in its documentation, in the Protocol page, we have:

Hello! While reading the Limine protocol specification i noticed that it says that "all non-usable entries (including kernel/modules) are not guaranteed any alignment, nor is it guaranteed that they do not overlap other entries". How am I supposed to get the memory size then? If the memory map entries can overlap, then summing their lengths won't work. Any help is appreciated, thanks in advance.

That's the Limine bootloader

It's way easier to use a pre-existing bootloader. I recommend Limine. It has it's own boot protocol that's designed for x86_64. You don't need any additional setup as it's already booted to long mode unlike Multiboot which needs you to switch to long mode since it's booted in protected mode. You can find an example kernel here.

It uses Limine as the Bootloader but I used Ponchos OS Dev Playlist as a base.

You can edit UEFI drivers from the operating system's bootloader, and you can even flash the UEFI itself from the OS in most computers. While secure boot. Failing that, you can shim a preloader between the bootloader and the UEFI and load arbitrary drivers despite secure boot, like is done here : https://github.com/ValdikSS/Super-UEFIinSecureBoot-Disk

Any sufficiently motivated attacker can make a UEFI rootkit happen, and it's in the wild right now. TPM really do offer no protection to users, either against userspace malware, or rootkits. It's purely about DRM.

Badabing badaboom

I was able to get around this by using a signed grub bootloader instead. What I did was modify a minimal grub disk from here to point to my manjaro installation using the partition uuid in its grub config. Its basically used to bypass secure boot and chainload the default unsigned grub2 which will start the system.

Try this if you want FreeBSD on a Secure Boot PC. I do this on my work PC.

This project works pretty good getting around the forced secure boot with the VCS: https://github.com/ValdikSS/Super-UEFIinSecureBoot-Disk