From: Hansjoerg Lipp <hjlipp@web.de>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Passing luks passphrase from grub to systemd
Date: Mon, 16 Apr 2018 02:11:06 +0200 [thread overview]
Message-ID: <a215d375-6fb1-d01e-63f2-48d98fc6bbc2@web.de> (raw)
In-Reply-To: <2907407.5HaPOCmciK@natalenko.name>
Hello Oleksandr.
Am 16.04.2018 um 00:25 schrieb Oleksandr Natalenko:
>> as I'm stuck with a (non-EFI x86_64) system with encrypted root
>> partition, I have to enter the passphrase twice (grub needs it for
>> getting the kernel etc., systemd needs it for mounting the root
>> partition). This can be quite inconvenient, especially if the passphrase
>> is long and contains special characters, and grub assumes a different
>> keyboard layout.
>
> Just fill another LUKS slot with a randomly generated key file and add that
> file to your initramfs (which already resides on encrypted /boot, right?). If
> your distro cannot do that, you should probably fixing things there, not
> adding ugly hacks to the kernel.
Yes, I never considered this proof of concept code as a good solution (I
don't want to get it into the kernel!), it was meant as a starting point
for discussing whether there is need for some mechanism to get data like
this from the boot loader to the init process, and if so, how to do it
right (and it was actually fun to learn a bit about all this).
I'm thankful for your hint how I could solve my personal luks problem in
a clean way (although it somehow does not feel right to have a key file
accessible to probable malware while the machine is running; of course a
paranoid thought of me...).
Kind regards and thanks again
Hansjoerg
next prev parent reply other threads:[~2018-04-16 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 22:25 Oleksandr Natalenko
2018-04-16 0:11 ` Hansjoerg Lipp [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-15 19:06 Hansjoerg Lipp
2018-04-15 22:35 ` Gabriel C
2018-04-15 23:21 ` Hansjoerg Lipp
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a215d375-6fb1-d01e-63f2-48d98fc6bbc2@web.de \
--to=hjlipp@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@natalenko.name \
/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
all inboxes | Powered by JetHome®