From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: 21843@debbugs.gnu.org
Subject: bug#21843: Generated grub.cfg does not support encrypted roots
Date: Thu, 10 Mar 2016 10:17:46 +0100 [thread overview]
Message-ID: <8760wuy9mt.fsf@gnu.org> (raw)
In-Reply-To: <20160308193309.GA2251@solar> (Andreas Enge's message of "Tue, 8 Mar 2016 20:33:09 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> What is needed are the following two lines at the beginning of grub.cfg:
>
> insmod luks
> cryptomount -u 1aa...
>
> where 1aa... is the result of "cryptsetup luksUUID /dev/sda2".
>
> So the logic outlined in my previous message works:
> Determine the mapped-devices /dev/sdXY of type luks-device-mapping that
> lead to a file-system with needed-for-boot? set to #t.
> Using
> cryptsetup luksUUID /dev/sdXY
> determine a corresponding uuid 12345...0.
> If any such mapped-device exists, add
> insmod luks
> as the first line of grub.cfg. For any such mapped-device, add a line
> cryptomount -u 12345...0
> right after that.
IIUC we don’t *have* to pass the UUID to ‘cryptomount’; we could also
pass the device name, in GRUB format, which would allow us to use the
same strategy as in ‘grub-root-search’ in (gnu system grub)… with the
difficulty that we’d have to be able to map Linux /dev node names to
GRUB device names.
Furthermore, to allow users to specify a LUKS UUID as the ‘source’ of
their ‘mapped-device’ form, as in:
(mapped-device
(source (uuid "cb67fc72-0d54-4c88-9d4b-b225f30b0f44")) ;LUKS UUID
(target "root")
(type luks-device-mapping))
we’d have to extend <mapped-device-kind> with a method to resolve UUIDs
(in this case, to map a UUID to a /dev node.)
Thoughts? Looks like more work than I initially thought.
Besides, I think we should only worry about the mapped device(s) that
back / and /boot, rather than any mapped device, no?
Thanks for looking into it,
Ludo’.
next prev parent reply other threads:[~2016-03-10 9:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 15:52 bug#21843: Generated grub.cfg does not support encrypted roots Ludovic Courtès
2016-03-08 19:21 ` Andreas Enge
2016-03-08 19:33 ` Andreas Enge
2016-03-10 9:17 ` Ludovic Courtès [this message]
2016-03-10 9:48 ` Andreas Enge
2016-03-11 8:45 ` Ludovic Courtès
2016-03-16 20:40 ` Andreas Enge
2016-03-17 13:14 ` Andreas Enge
2016-04-17 23:29 ` Ludovic Courtès
2016-04-27 20:58 ` Ludovic Courtès
2016-05-01 22:07 ` Ludovic Courtès
2016-10-26 6:56 ` Christopher Baines
2016-11-23 20:21 ` Ludovic Courtès
2016-04-16 16:09 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760wuy9mt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=21843@debbugs.gnu.org \
--cc=andreas@enge.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).