From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 21843@debbugs.gnu.org
Subject: bug#21843: Generated grub.cfg does not support encrypted roots
Date: Wed, 16 Mar 2016 21:40:00 +0100 [thread overview]
Message-ID: <20160316204000.GA8709@solar> (raw)
In-Reply-To: <8760wuy9mt.fsf@gnu.org>
On Thu, Mar 10, 2016 at 10:17:46AM +0100, Ludovic Courtès wrote:
> 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.)
I just read a bit of the cryptsetup manual; we do not need to do the
resolution, in the above example we would have the line
cryptomount -u cb67fc72-0d54-4c88-9d4b-b225f30b0f44
(as discussed previously; it works at least without the dashes, we can also
try to keep the dashes).
And then it should be possible to open the device with
cryptsetup luksOpen UUID=cb67fc72-0d54-4c88-9d4b-b225f30b0f44 root
This looks for the given uuid in /dev/disk/by-uuid.
I wanted to give it a try with the installation image, but unfortunately it
does not contain the directory /dev/disk.
Andreas
next prev parent reply other threads:[~2016-03-16 20:41 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
2016-03-10 9:48 ` Andreas Enge
2016-03-11 8:45 ` Ludovic Courtès
2016-03-16 20:40 ` Andreas Enge [this message]
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=20160316204000.GA8709@solar \
--to=andreas@enge.fr \
--cc=21843@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).