Follow-up Comment #7, bug #47108 (project grub):
Only sda5 is necessary to boot. The other drive is mounted after boot. I might
even want to put the key on a flash drive in the future.
But here's the problem:
/boot is encrypted.
It does not have access to /boot/grub/grub.cfg until after I give it the
passphrase for sda5 (hd0,msdos5).
What would be useful is for it do something like this:
Encrypted partition found hd0,msdos5.
Choose (P)assphrase, (E)xternal key, (N)etwork auth, (S)kip, (D)one: P
Enter passphrase:
Slot 0 opened
Encrypted partition found hd1,msdos1.
Choose (P)assphrase, (E)xternal key, (N)etwork auth, (S)kip, (D)one: S or D
Skipping mount
Or even better
Partitions found (* encrypted): hd0,msdo5 (h0m5)*, hd1,msdos1 (h1m1)*
Enter list of partitions to access for boot (shortnames accepted): h0m5
Choose (P)assphrase, (E)xternal key, (N)etwork auth, (S)kip, (D)one: P
Enter passphrase:
Slot 0 opened
Also could embed small bare minimum configuration vars in boot sector
GRUB_BOOT_ACTIVATION_LIST="hd0,msdos5=passphrase:hd1,msdos1=external"
What do I need to set up on debian to test the GIT release?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47108>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-grub mailing list
Bug-grub@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-grub
