From: ludo@gnu.org (Ludovic Courtès)
To: Eddie Baxter <pieceredd@gmail.com>
Cc: bug-guix@gnu.org, help-guix@gnu.org
Subject: LUKS-encrypted root and unencrypted /boot with GuixSD 0.12.0
Date: Sat, 31 Dec 2016 00:52:04 +0100 [thread overview]
Message-ID: <87inq16km3.fsf@gnu.org> (raw)
In-Reply-To: <CAOXwz5_i2-dUVeFgNfXt07zazCq1SLz6V+WGC09JLRYzUgUDRA@mail.gmail.com> (Eddie Baxter's message of "Thu, 29 Dec 2016 23:37:10 +0000")
Hello!
Eddie Baxter <pieceredd@gmail.com> skribis:
> I have attempted to install GuixSD on an encrypted root using LUKS, after
> reading the release notes for 0.12.0 that implies this should now work - My
> config.scm is linked:
>
> https://gist.github.com/AcouBass/3a1a6ab28c17830a175dc7da95eb18cd
>
> I don't get any errors on installation, nor upon doing a system
> reconfigure.
>
> At the moment I am still having to drop to a command prompt in Grub and use
> the commands:
>
> insmod luks
> cryptomount hd0,msdos2
The config has an unencrypted /boot and an encrypted root. What’s
tested and known-good is a configuration with an encrypted root that
contains /boot, like the one here:
https://www.gnu.org/software/guix/manual/html_node/Using-the-Configuration-System.html#index-encrypted-disk-1
It may be that this configuration is not correctly supported yet.
I’m Cc’ing bug-guix@gnu.org so we keep track of this issue.
> Which while it does work does mean I'm entering my passphrase twice
> (As well as having to drop to the Grub command line!)
The passphrase-twice issue seems hard to avoid: first GRUB needs to
access the partition, and then the kernel needs to access it.
If anyone is aware of ways to solve this, I’m all ears!
Thanks for your report!
Ludo’.
next parent reply other threads:[~2016-12-30 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOXwz5_i2-dUVeFgNfXt07zazCq1SLz6V+WGC09JLRYzUgUDRA@mail.gmail.com>
2016-12-30 23:52 ` Ludovic Courtès [this message]
2020-11-16 17:56 ` bug#25305: LUKS-encrypted root and unencrypted /boot with GuixSD 0.12.0 Jonathan Brielmaier
2020-11-18 16:54 ` Danny Milosavljevic
2020-11-18 17:46 ` 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=87inq16km3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=help-guix@gnu.org \
--cc=pieceredd@gmail.com \
/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).