From: Joshua Branson <jbranso@dismail.de>
To: Thomas Albers <tgalbers2000@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Typing LUKS passphrase only once and a possible solution
Date: Wed, 07 Jul 2021 14:12:26 -0400 [thread overview]
Message-ID: <878s2i0z91.fsf@dismail.de> (raw)
In-Reply-To: <87k0m2gld3.fsf@gmail.com> (Thomas Albers's message of "Wed, 07 Jul 2021 18:05:44 +0200")
Thomas Albers <tgalbers2000@gmail.com> writes:
> Hello everyone,
>
> I recently installed guix on my X200T and through the process I found
> some challenges I was not not solve by myself. Its nothing strictly
> necessary but I would like to solve them nonetheless.
>
> My current setup consists of libreboot, my main luks partition and a
> lvm group inside.
I'm a little jealous. I haven't figured out how to set up an encrypted
/. Did you encrypt your /boot as well!? I've got a osboot-ed T400.
> The problem I mentioned is the necessity of typing the passphrase for
> the luks device twice. Once for the bootloader and again for the
> kernel itself.
I've heard that this is the "most" secure way of booting. Though I'm no
security expert. :)
> In other distributions this is avoided by copying a key file into the
> initramfs and passing the kernel parameter "cryptkey" to linux. So
> naturally the first I tried after not finding any documentation on
> this topic was this, albeit without success.
I don't think that we have a guix-y way of doing this yet. Though I
would love it if we did!
Your other questions have moved past my expertise. I wish I could be
more help. :)
>
> Thomas Albers Raviola
>
--
Joshua Branson (jab in #guix)
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
https://propernaming.org
"You can have whatever you want, as long as you help
enough other people get what they want." - Zig Ziglar
next prev parent reply other threads:[~2021-07-07 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 16:05 Typing LUKS passphrase only once and a possible solution Thomas Albers
2021-07-07 16:42 ` Tobias Geerinckx-Rice
2021-07-07 18:29 ` Thomas Albers
2021-07-08 17:29 ` Vagrant Cascadian
2021-07-07 18:12 ` Joshua Branson [this message]
2021-07-07 18:30 ` Wiktor Żelazny
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=878s2i0z91.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=help-guix@gnu.org \
--cc=tgalbers2000@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.
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).