github doug445/AsahiLocker v2.1.0
AsahiLocker 2.1.0

one hour ago

AsahiLocker 2.1.0: encrypt from RAM

A third way to run AsahiLocker, alongside the live USB and the second install. It's for Macs whose U-Boot never sees a USB stick, and it needs neither a stick nor a second install.

sudo ./AsahiLocker/bin/ram-rescue.sh build --arm && sudo reboot
# at the rescue prompt:
asahilocker

bin/ram-rescue.sh builds a rescue initramfs from your own kernel. It carries luks-deploy.sh, every tool that script needs, and the cracklib dictionary. GRUB boots it with nothing on the disk mounted, and asahilocker encrypts the root partition in place. Afterwards, ram-rescue.sh remove takes it away again. Full walkthrough: docs/RAM-RESCUE.md.

  • Survives a power cut. The rescue finds your partitions by GPT partition UUID, which doesn't change during encryption, and boots straight to its prompt. Choose it in the GRUB menu, type asahilocker again, and the encryption resumes.
  • Your GRUB files are untouched. The entry lives in its own file, /etc/grub.d/42_asahilocker-rescue; 40_custom is never edited.
  • Weak passphrases are still refused. The dictionary is in the image. In any other minimal environment, luks-deploy.sh borrows the target's own dictionary for the run.
  • No keys in the logs. The rescue writes its logs to /boot/asahilocker-rescue-logs/; the recovery key and the header backup are never copied there.

luks-deploy.sh

  • Runs from a RAM-only rescue (#5, #6, thanks to @kernelzeroday). The recovery material is copied onto the encrypted system at the end of the run.
  • Checks that the target has its initramfs and GRUB tools before anything is written.
  • Creates /mnt if it is missing, and retries a resume once after cryptsetup repair.

Tested end to end in a KVM guest running the official Fedora Asahi Remix 45 image. Not yet run on Apple hardware.

Don't miss a new AsahiLocker release

NewReleases is sending notifications on new releases.