Encrypted installs can unlock root in the initramfs #53
No reviewers
Labels
No labels
P0
P1
P2
P3
audio
bakery
boot
breadbug
bug
build
ci
dependencies
design
disk
docs
encryption
final
firewall
graphics
hardware
idle
installer
keybinds
nvidia
packages
phase-1
polish
recovery
reliability
reproducibility
secure-boot
security
shell
signing
snapshots
supply-chain
swap
tech-debt
theming
ux
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Breadway/bos!53
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/bos-23-initramfs-luks-unlock"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Calamares now registers an encrypted-root boot keyfile before fstab, and the installer prepares the matching mkinitcpio hook and keyfile before initramfs generation. GRUB receives the LUKS container UUID and mapper name for the selected hook; the smoke test checks encrypted boot parameters.
Verified:
bash -nfor the changed scripts, YAML parsing for the Calamares settings,git diff --check, andFAST_BUILD=1ISO build. The build completed with an existingnbd-clientinitramfs package-hook warning. Encrypted UEFI and BIOS VM installs were not run, so the issue remains in doing until those boot checks are confirmed.Closes #23
This PR card tracks BOS-23 / PR #53. Encrypted UEFI and BIOS installation acceptance is still missing; reviewer found the PR unmergeable. Parent BOS-23 is TODO. Synchronizing card status to TODO.
PR #53 has the implementation and static wiring checks recorded on the rebased head. Fresh encrypted UEFI/BIOS Calamares installs and boot-to-breadgreet acceptance remain outstanding; BOS has no ordinary push CI. Moving the implementation to REVIEW for the requested handoff. Do not treat as verified or done until those acceptance checks are recorded.