From: "Alex Griffin" <a@ajgrf.com>
To: guix-devel@gnu.org
Subject: Re: Unencrypted boot with encrypted root
Date: Tue, 07 Apr 2020 15:05:05 +0000 [thread overview]
Message-ID: <135d8491-53e8-46b6-b77a-fe6a4539b15d@www.fastmail.com> (raw)
In-Reply-To: <87d08jbpcc.fsf@gnu.org>
On Tue, Apr 7, 2020, at 9:46 AM, Ludovic Courtès wrote:
> The difficulty is that any file traveling through the store is
> world-readable. It’s hard to avoid.
If we can create the key file outside of the store, then GRUB is capable of being passed multiple initrds. So we can put the key in its own initrd (outside of the store), continue to generate the normal initrd in /gnu/store, and pass both of them to GRUB. The key never enters the store in any way.
The result is that the user only needs to enter a password into GRUB, because GRUB then passes the key file to the kernel.
--
Alex Griffin
next prev parent reply other threads:[~2020-04-07 15:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 8:59 Unencrypted boot with encrypted root Pierre Neidhardt
2020-04-03 15:32 ` pelzflorian (Florian Pelz)
2020-04-03 15:44 ` Ellen Papsch
2020-04-03 16:13 ` Pierre Neidhardt
2020-04-03 17:16 ` Ellen Papsch
2020-04-03 19:56 ` Guillaume Le Vaillant
2020-04-04 9:02 ` Pierre Neidhardt
2020-05-17 15:39 ` Pierre Neidhardt
2020-05-20 8:49 ` Guillaume Le Vaillant
2020-05-20 9:42 ` Pierre Neidhardt
2020-04-03 19:44 ` pelzflorian (Florian Pelz)
2020-04-04 8:12 ` Ellen Papsch
2020-04-04 10:18 ` pelzflorian (Florian Pelz)
2020-04-06 12:00 ` Ellen Papsch
2020-04-07 9:46 ` Ludovic Courtès
2020-04-07 11:34 ` Ellen Papsch
2020-04-07 20:19 ` Ludovic Courtès
2020-04-08 12:37 ` Ellen Papsch
2020-04-07 15:05 ` Alex Griffin [this message]
2020-04-07 16:47 ` Vagrant Cascadian
2020-04-08 12:25 ` Ellen Papsch
2020-04-08 15:07 ` Alex Griffin
2020-04-08 16:22 ` Vagrant Cascadian
2020-04-08 7:57 ` Pierre Neidhardt
2020-04-08 12:19 ` Alex Griffin
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=135d8491-53e8-46b6-b77a-fe6a4539b15d@www.fastmail.com \
--to=a@ajgrf.com \
--cc=guix-devel@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).