Tags: anatol/booster
Tags
Release Booster 0.13 with major encrypted-boot improvements Booster 0.13 is a big step forward for encrypted-boot usability, bringing smoother, more reliable, and more flexible unlock flows. Highlights include native early-boot SSH unlock, Plymouth boot splash support, expanded crypttab integration, detached LUKS header support, external keyfile support, native FIDO2 handling, newer TPM2 token support, configurable token orchestration, and passphrase caching for multi-device LUKS unlocks. This release also improves prompt cancellation across keyboard, Plymouth, SSH, FIDO2, and TPM2 paths, makes generator output more deterministic, hardens image unpacking, improves diagnostics, fixes several boot-time races, and refreshes documentation for the new encrypted-boot workflows. Huge thanks to all contributors for making this a bright and exciting release for secure, practical, and polished encrypted boot!
Booster 0.7 release * Fixed a race condition with mounting RAID5 volumes. (#97) * Added support for custom encryption blocks. With cryptsetup 2.4.0 LUKS partitions use large encryption blocks of size 4096 bytes. * Add support of sha512 and blake2b/blake2s hashes to pbkdf2 KDF. * Add support of FIDO2 and TPM2 tokens enrolled with systemd-cryptenroll. (#96) * Booster now waits till `modules_force_load` modules are fully loaded before switching to userspace. (#103) * Add compatibility support for proprietary drivers. It makes possible to load `amdgpu` at boot time. (#45 #104) * nvme and usb could be used as root devices now. (#94 #95) * HID drivers `kernel/drivers/hid` are checked by default now. This improves keyboard drivers detection and fixes numerous keyboard issues at the boot time. (#80) * By default network modules removed from the image if network is disabled in config. This reduces size of the generated image. * Improves [Discoverable Partitions Specification](https://systemd.io/DISCOVERABLE_PARTITIONS/) compliance. Booster makes sure that only root from active ESP disk is mounted; booster is able to detect LUKS partitions and mount them; booster takes GPT flags into account. (#98) * It is possible to specify a LUKS partitions as `root=` directly. In this case the LUKS partition is unlocked and mounted as `/dev/mapper/root`.
Booster 0.4 release * Speedup image generation with optimized modalias matching. (#41) * Add 'fsck' support. If fsck binary is added to the image then it is called right before the root block device is mounted. (#32) * Add support for stripping ELF binaries. It helps to reduce image size. (#36) * At the end of initramfs process booster removes content of tmpfs to reclaim initramfs memory back to the system. (8415258) * Add support for virtual console configuration. It is possible to use non-ASCII keyboard/font configuration at the boot time now. (#43) * Add a script to regenerate booster images for all installed kernels. It is useful in case if a configuration is changed and the user wants to update these images. (b3dd4f5) * Add a new network configuration option to specify what interfaces should be initialized at the boot time. Useful in case if a host has multiple networks but only one of them should be used. (#25) * Firmware files for kernel modules added to image automatically. (#48) * Host mode handles builtin modules correctly now. (#54) * Booster honors `quiet` boot option now. If it is specified then only error messages are printed out to the console. (#39) * Add support for kernel modules compressed with lz4 (#34) and gzip (#55). * Add support for initramfs compressed with xz. (#42) * booster handles UUID boot params with quotes e.g. root=UUID="foo-bar-some-UUID" (#6) * Add possibility to exclude some of the default modules from the image. (#3) * Add `modules_force_load` config option to specify modules that need to be additionally loaded at the boot time. (#20) * Add a boot flag to disable concurrent module loading. It helps to get a cleaner debug log. (#61) * Add 'resume=' boot option support (#49) * Booster logs are printed to kmsg and available at host via `dmesg` and `journalctl`. (#60) * Handle kernel module parameters specified via modprobe.d and boot parameters e.g. "vfio-pci.ids=1002:67df,1002:aaf0" (#20 #62 #74). As a result booster handles GPU passthrough using vfio now.
PreviousNext