efifs
sbctl
efifs | sbctl | |
---|---|---|
11 | 94 | |
495 | 1,304 | |
- | - | |
0.0 | 7.8 | |
20 days ago | 4 days ago | |
C | Go | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
efifs
-
How to Boot ISO Files from GRUB2 Boot Loader
See also UEFI drivers that can read a bunch of other file systems (btrfs, ext2/3/4, HFS, ISO, NTFS, UFS/FFS, XFS, ZFS, etc):
* https://efi.akeo.ie
* https://github.com/pbatard/efifs
The UEFI spec specifies (§13.3) that firmware is only required to read FAT32/16/12, which is generally why your /boot/efi is VFAT/FAT32.
-
Is exFAT bootable?Can I boot WinPE with exFAT?
In theory you would still need a FAT32 efi 'stub' partition with the exFAT filesystem drivers which you have to load before loading the WinPE loader (bootmgfw.efi).
-
How do I configure the refind.conf and refind_linux.conf (and or config.yaml (for ZFSBootMenu)) files properly when installing Arch Linux with ZFS Native Encryption?
I am pretty sure that that I am doing something incorrectly with the configuration files for the rEFInd bootloader, but everything else should be correct. However, as I write this, I barely realized did I not use the following commands recommended from the "Usage" section from the aforementioned website where I downloaded the zfs_x64.efi driver file for rEFInd:
-
Grub vs Systemd-boot --removable question
I found the drivers here https://efi.akeo.ie/ . Which means, that any EFI bootloader able to load them will be able to use them. They are not for bootloader, but it is the firmware which will use them. As i said, i am little bit afraid that it will not work on any board as some manufacturers have pretty buggy firmware when talking about infrequently used features. Also i am bit unsure they will work with secure boot as they are gpl3 thus will be never signed by Microsoft and i don't know what UEFI requirements for drivers are in this regard.
-
Why use a bootloader? Just boot directly into a unified kernel image
Even for those using systemd-boot with custom efi drivers to provide functionality, it's worth noting that those drivers are being developed downstream of GRUB.
- Latest grub update on arch distros seems to cause boot issues
-
So why do so people still use GRUB?
I think you can also add btrfs filesystem support for sd-boot by including the EFI drivers for it on the EFI partition instead, from https://github.com/pbatard/efifs/releases I think. Haven't tried it myself though.
- Is any ESP filesystem other than vfat supported on coreboot? (lemp9)
-
Fedora considers deprecating legacy BIOS
EFI doesn't actually mandate FAT for the system partition. The system partition can be any filesystem that the firmware supports.
Of course, pretty much all EFI implementations only support FAT, so it's a bit of a moot point; the only one I'm aware of that supports anything else is the one on Intel Macs, which also understands HFS+.
You can find a huge selection of EFI filesystem drivers at https://efi.akeo.ie/ but they're derived from GRUB and hence GPL, so don't expect the likes of American Megatrends to be bundling these any time soon.
- Help Please! I rebooted my TrueNAS SCALE and get the following.
sbctl
- Show HN: Sbctl – Secure Boot key manager
-
Show HN: SSH-tpm-agent – SSH agent for TPMs
No, this isn't true nor correct.
Secure Boot and TPM do offer tangible security benefits and is security features you can take ownership of.
Secure Boot allows your own key hierarchy, and TPM allows you to take ownership.
The linked boot disk isn't really proof that Secure Boot is useless. If you don't set a MOKManager password (as you should), and you change the security state of the machine while present at the keyboard. Yes you can boot things.
This is intended to make sure people can actually decide to trust things. And having insecure defaults makes this less useful. Not very surprising.
TPMs could also prevent attacks like this on your machine.
Incidentally I've invested quite a bit of time in making user-friendly Secure Boot tooling as well. https://github.com/Foxboron/sbctl
-
Enabling secure boot for your Arch installation is very easy now with the "sbctl" tool
No problem! The sbctl package ships with a pretty extensive hook out of the box (https://github.com/Foxboron/sbctl/blob/master/contrib/pacman/ZZ-sbctl.hook). It's been very reliable for automatically resigning .efi executables after updates for me.
-
sbctl fails to find EFI system partition
sbctl verify returns failed to find EFI system partition despite it definitely is there. It's the same issue as this but remounting or restarting doesn't fix it.
-
Millions of PC Motherboards Were Sold With a Firmware Backdoor
lol
- The vendor-locking is for your own safety. Do not resist.
-
Let's make a motherboard review guide
Must actually prevent unsigned images from booting
-
[Kinoite/Silverblue]Decrypt LUKS volumes with a TPM on Fedora 35+
sudo dnf install asciidoc golang -y VERSION=0.11 cd /tmp curl -L "https://github.com/Foxboron/sbctl/releases/download/${VERSION}/sbctl-${VERSION}.tar.gz" | tar zxvf - cd "sbctl-${VERSION}" make sudo make install cd ~
-
Setting up secure boot while dual booting Windows 11 and Arch Linux
By far the easiest is to use sbctl to generate, install and use keys to sign your efi images. You can use mkinitcpio to build the unified kernels automatically and a pacman trigger to rerun the sbctl signing when the kernel is updated. Pretty straightforward (once you've done it once).
-
Intel OEM Private Key Leak: A Blow to UEFI Secure Boot Security
The question is whether you have any UEFI drivers or not. If they're in the ESP you can just look there to check, but UEFI drivers can also be loaded from PCI cards or baked in the firmware itself.
If you're using a TPM for Secure Boot, you can use the command in https://github.com/Foxboron/sbctl/wiki/FAQ#option-rom to know for sure.
What are some alternatives?
uefi-elf-bootloader - UEFI ELF Bootloader example
mortar - Framework to join Linux's physical security bricks.
ReBarUEFI - Resizable BAR for (almost) any UEFI system
mkinitcpio - Arch Linux initramfs generation tools (read-only mirror)
swtpm - Libtpms-based TPM emulator with socket, character device, and Linux CUSE interface.
zorin-exec-guard - Zorin Exec Guard shows a warning when attempting to run unknown Linux or Windows executables and offers more trusted alternatives.
cryptboot - Encrypted boot partition manager with UEFI Secure Boot support
BootDuet - Boot sector program for booting Intel's EDK Developer's UEFI Emulation (DUET) from hard disk with LBA.
mainline - Install mainline kernel packages from kernel.ubuntu.com
uefi-ntfs - UEFI:NTFS - Boot NTFS or exFAT partitions from UEFI
simple-arch-installer