all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
Cc: "Jakub Kądziołka" <kuba@kadziolka.net>, 38924@debbugs.gnu.org
Subject: bug#38924: Encrypted root volume requires passphrase twice on boot
Date: Sat, 04 Jan 2020 20:56:44 +0100	[thread overview]
Message-ID: <87woa73shv.fsf@nckx> (raw)
In-Reply-To: <87pnfznhsw.fsf@mattleach.net>

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

Matthew,

Matthew Leach 写道:
> I've setup guix on two machines each one of them with an 
> encrypted root
> partition. However, on boot I'm prompted for my passphrase 
> twice, once
> before the grub menu is shown and second after Linux has started 
> and
> launched guile as init.

Unfortunately, this is expected.

GRUB needs to decrypt the volume to load the Linux-Libre kernel 
and initrd, and there's no agreed-upon secure way for GRUB to pass 
the passphrase or key to the kernel/initrd.  So you're prompted 
for it again when the volume is actually mounted by the kernel.

> I would expect to have to only enter my passphrase once per 
> boot.

Most distributions hack around this limitation by including the 
unencrypted LUKS key in the initrd on the encrypted volume itself. 
Guix doesn't currently have any code to do the same.

This has been a problem for years but, by sheer coincidence, Jakub 
Kądziołka (CC'd) mentioned that this was on their to-do list for 
next week.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2020-01-04 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-04 19:27 bug#38924: Encrypted root volume requires passphrase twice on boot Matthew Leach
2020-01-04 19:56 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87woa73shv.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=38924@debbugs.gnu.org \
    --cc=kuba@kadziolka.net \
    --cc=me@tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.