sbctl
cryptboot
sbctl | cryptboot | |
---|---|---|
94 | 5 | |
1,304 | 199 | |
- | - | |
7.8 | 0.0 | |
4 days ago | 5 months ago | |
Go | Shell | |
MIT License | GNU General Public License v3.0 only |
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.
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.
cryptboot
-
Setting up Secure Boot, but the wiki doesn't provide enough info I think
I just completely cheated by using cryptboot. Then it is as simple as cryptboot-efikeys create, then to enroll them into your eufi, cryptboot-efikeys enroll and finally to sign any efi executable (or any file), cryptboot-efikeys sign $FILE. There are other helper scripts, but I don't use them. Full documentation is on their GitHub: https://github.com/xmikos/cryptboot. Good luck!
- Authenticated Boot and Disk Encryption on Linux
-
Physical security tips & recommendations
Prevent evil maid by bringing your devices everywhere. Or you can just switch to GNU/Linux and add https://github.com/xmikos/cryptboot
-
Unencrypted boot partition risks
I think it was this one: https://github.com/xmikos/cryptboot
-
Cool new things on linux world for fresh installation and a bit of my usage different things.
Also, I am pretty sure that you can only have encrypted /boot if you use GRUB. The point of doing so is not really to make sure nobody reads it (there isn't anything interesting on /boot by default), but to make sure that nobody can tamper with it (ignoring the encryption vs authenticated encryption discussion). However, you still have to make sure nobody can tamper with GRUB itself. You might want to check out https://github.com/xmikos/cryptboot if this sounds interesting. Also, there are similar solutions that don't use encrypted /boot, for example booting from signed EFISTUBs, see https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface/Secure_Boot#Implementing_Secure_Boot. Also, I don't actually use this kind of setup personally (albeit I'd like to one day), and I am certainly not a security expert, so take this whole paragraph with a big grain of salt, and double check with somebody who actually knows what they are talking about.
What are some alternatives?
mortar - Framework to join Linux's physical security bricks.
dotfiles - :unicorn: My personal dotfiles
mkinitcpio - Arch Linux initramfs generation tools (read-only mirror)
heads - A minimal Linux that runs as a coreboot or LinuxBoot ROM payload to provide a secure, flexible boot environment for laptops, workstations and servers.
zorin-exec-guard - Zorin Exec Guard shows a warning when attempting to run unknown Linux or Windows executables and offers more trusted alternatives.
safeboot - Scripts to slightly improve the security of the Linux boot process with UEFI Secure Boot and TPM support
mainline - Install mainline kernel packages from kernel.ubuntu.com
sbupdate - Generate and sign kernel images for UEFI Secure Boot on Arch Linux
simple-arch-installer
tpm2-totp - Attest the trustworthiness of a device against a human using time-based one-time passwords