sbupdate
cryptboot
sbupdate | cryptboot | |
---|---|---|
9 | 5 | |
223 | 198 | |
- | - | |
0.0 | 0.0 | |
9 months ago | 5 months ago | |
Shell | Shell | |
GNU General Public License v3.0 only | 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.
sbupdate
-
Getting LUKS, Btrfs, Hibernation and Swap file working in tandem
I use sbupdate [0] to build the unified kernel image and to sign it with my keys. It's run by a hook in the arch's package manager whenever the kernel, the initrd or the firmware images change. I saw the other day that systemd recently got an utility to do this, but I've never looked into that. sbupdate has been working fine for me for several years now.
It doesn't store a new key in the uefi, it signs the new image with the key that uefi already knows about.
See [1] for the whole setup and [2] for the signing part specifically.
[0] https://github.com/andreyv/sbupdate
[1] https://wiki.archlinux.org/title/Unified_Extensible_Firmware...
[2] https://wiki.archlinux.org/title/Unified_Extensible_Firmware...
- Secure boot, sbupdate and systemd-boot
-
Can someone help me navigate the BIOS settings without display?
Here is where different systems will fork. On Arch there is a pacakge sbupdate where it automatically generate unified kernel images using pacman hooks and I use systemd-boot (which must be signed by your keys) to load it.
-
Windows 11 requiring to turn on Secure boot, making dual boot a little harder
I really think it's easy enough. You create your keys, put them into /etc/efi-keys, enroll them into your UEFI by whatever method you prefer, install sbupdate-git and you're done... You need to run sbupdate manually once after install, everything else works automatically through hooks.
-
I've moved to a new laptop with 3 NVMe drives, and I want full encryption and Secure Boot.
Ah, sbupdate does that very well; it embeds the kernel image, initramfs and the UEFI boot image into a unified signed image. I presume this signed image should then be further encrypted?
-
Unencrypted boot partition risks
Check out https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface/Secure_Boot and https://github.com/andreyv/sbupdate
-
Cool new things on linux world for fresh installation and a bit of my usage different things.
For the last part, check out https://github.com/andreyv/sbupdate . Linked also from arch wiki, so not some completely random solution. Its for creating unified kernel images, including the initramfs, microcode and so on. This package is then signed for secureboot, and can be loaded using EFISTUB for example. This prevents attacks against initramfs or some other things on /boot, if unencrypted. I haven't come around to test it myself, but I think its a neat solution, and with proper secure boot (and password protected firmware), a reasonable protection against evil maid attacks.
-
Security
I am using secure boot with custom keys, a fully encrypted root btrfs partition with /boot on it, with swap also encrypted with hibernation support. The only non-encrypted partition is the EFI partition with boot images signed with https://github.com/andreyv/sbupdate (look up "direct booting").
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?
clevis - Automated Encryption Framework
sbctl - :computer: :lock: :key: Secure Boot key manager
antibody - The fastest shell plugin manager.
dotfiles - :unicorn: My personal dotfiles
ohmyzsh - 🙃 A delightful community-driven (with 2,300+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python, etc), 140+ themes to spice up your morning, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.
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.
safeboot - Scripts to slightly improve the security of the Linux boot process with UEFI Secure Boot and TPM support
zsh-syntax-highlighting - Fish shell like syntax highlighting for Zsh.
mortar - Framework to join Linux's physical security bricks.
tpm2-totp - Attest the trustworthiness of a device against a human using time-based one-time passwords