From: Benjamin Slade <beoram@gmail.com>
To: help-guix@gnu.org
Subject: Re: LUKS-encrypted root and unencrypted /boot ?
Date: Fri, 03 Aug 2018 11:07:19 -0600 [thread overview]
Message-ID: <878t5nfkfs.fsf@jnanam.net> (raw)
In-Reply-To: <877el9ch1c.fsf@gmail.com>
On 2018-08-02T02:24:31-0600, Chris Marusich <cmmarusich@gmail.com> wrote:
> > 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?
> At that stage, is it GRUB that is unlocking the encrypted volume? If
> so, I think this is normal.
> For what it's worth, GRUB is slow in unlocking my encrypted volumes,
> too. It takes about 30 seconds for me, too. If you're concerned,
> you can try using cryptsetup's --iter-time option to lower the number
> of iterations, but keep in mind that will also make it easier to
> crack your passphrase.
Originally I had --iter set to '5000' and it took about 4 minutes to
unlock! I've shifted to using an unencrypted root and an encrypted
/home as a compromise that boots faster (and only requests the password once).
--
Benjamin Slade - https://babbagefiles.xyz
`(pgp_fp: ,(21BA 2AE1 28F6 DF36 110A 0E9C A320 BBE8 2B52 EE19))
'(sent by mu4e on Emacs running under GNU/Linux . https://gnu.org )
`(Choose Linux ,(Choose Freedom) . https://linux.com )
prev parent reply other threads:[~2018-08-03 17:07 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
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 [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
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=878t5nfkfs.fsf@jnanam.net \
--to=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).