From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
My screen flashes gray three times before rEFInd shows up
That's your firmware and/or rEFInd's fault. Tweaking flags for the Linux kernel will do nothing here.
Intel iGPUs can do flicker-free boot from the bootloader on.
Is there anyway I can get an encrypted Garuda system to work with Secure Boot?
What do you need secure boot for?
What do you need secure boot for?
Probably to ensure their system isn't tampered with? Depending on who you hang with, that may be in your threat model.
Secure boot is only one small link in a chain of things that need to be working in order to have a system that is only halfway resistant against evil maids.
If you're running Garuda, the rest of the chain is not present in any way.
Secure boot + encryption is enough for evil maids. They already said they had an encrypted system.
Secure boot + encryption willy happily boot the maid's initrd.
No, because either the initrd is signed, built into a signed unified kerbel image, or it's encrypted like on my setup (where everything but the grubx64.efi binary is encrypted and that binary is signed).
You mean, like, there's some more setup you need to do in order to build some actual resistance against evil maids; making secure boot a small part of a greater link?
Also, I still wouldn't count such a setup as "half-way resistant against evil maids" as, in a setup like you describe, it's almost trivial for an evil maid to go into firmware to disable secure boot and install their own bootloader instead of yours.
Well, they don't seem to be replying to this post, so I guess we will never know if they have a BIOS password or even are signing or encrypting their initrd.
I still can't figure out how to tag people from eternity (infinity for lemmy).
Check out sbctl (for secure boot) https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot#Assisted_process_with_sbctl