From: "Clément Lassieur" <clement@lassieur.org>
To: Benjamin Slade <beoram@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: LUKS-encrypted root and unencrypted /boot ?
Date: Thu, 02 Aug 2018 08:59:51 +0200 [thread overview]
Message-ID: <87effh8d94.fsf@lassieur.org> (raw)
In-Reply-To: <87in4tgbg4.fsf@jnanam.net>
Hi Benjamin,
Do you use Libreboot?
Benjamin Slade <beoram@gmail.com> writes:
> Doing a full LUKS-encryption on root, including /boot results in very
> slow unlocking at boot (about 30 secs even with --iter set to 1000). Is
> there any way to do an unencrypted /boot with an encrypted root?
I'm unsure that would help, because GRUB would still have to unencrypt /
to access the kernel (the kernel is in /gnu/store).
Clément
next prev parent reply other threads:[~2018-08-02 6:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 18:59 LUKS-encrypted root and unencrypted /boot ? Benjamin Slade
2018-08-02 6:59 ` Clément Lassieur [this message]
2018-08-03 17:05 ` Benjamin Slade
2018-08-03 18:53 ` Clément Lassieur
2018-08-04 15:30 ` Benjamin Slade
2018-08-04 15:48 ` Clément Lassieur
2018-08-04 21:14 ` Benjamin Slade
2018-08-05 5:26 ` Chris Marusich
2018-08-02 8:24 ` Chris Marusich
2018-08-03 17:07 ` Benjamin Slade
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=87effh8d94.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=beoram@gmail.com \
--cc=help-guix@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.
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).