From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Ellen Papsch <ellen.papsch@wine-logistix.de>
Cc: guix-devel@gnu.org
Subject: Re: Unencrypted boot with encrypted root
Date: Sat, 4 Apr 2020 12:18:32 +0200 [thread overview]
Message-ID: <20200404101832.cmegsybfyrseazjq@pelzflorian.localdomain> (raw)
In-Reply-To: <a96461003ce1ff51cf8a39cdb56a8685c2e2a8dd.camel@wine-logistix.de>
Thank you Ellen for the good summary. I knew most but in less detail.
On Sat, Apr 04, 2020 at 10:12:46AM +0200, Ellen Papsch wrote:
> Am Freitag, den 03.04.2020, 21:44 +0200 schrieb pelzflorian (Florian
> Pelz):
> > But it would still be possible for an attacker […]
> Yes, though it should not be so easy like with unprotected /boot
> partition.
So the better solution would be a better GRUB instead of unprotected
/boot. Could key files help in passing the passphrase on to the Linux
kernel? The Arch Wiki says this:
<https://wiki.archlinux.org/index.php/Dm-crypt/Device_encryption#With_a_keyfile_embedded_in_the_initramfs>.
Keyboard layouts then will only all work properly everywhere once
fixed in GRUB.
Regards,
Florian
next prev parent reply other threads:[~2020-04-04 10:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 8:59 Unencrypted boot with encrypted root Pierre Neidhardt
2020-04-03 15:32 ` pelzflorian (Florian Pelz)
2020-04-03 15:44 ` Ellen Papsch
2020-04-03 16:13 ` Pierre Neidhardt
2020-04-03 17:16 ` Ellen Papsch
2020-04-03 19:56 ` Guillaume Le Vaillant
2020-04-04 9:02 ` Pierre Neidhardt
2020-05-17 15:39 ` Pierre Neidhardt
2020-05-20 8:49 ` Guillaume Le Vaillant
2020-05-20 9:42 ` Pierre Neidhardt
2020-04-03 19:44 ` pelzflorian (Florian Pelz)
2020-04-04 8:12 ` Ellen Papsch
2020-04-04 10:18 ` pelzflorian (Florian Pelz) [this message]
2020-04-06 12:00 ` Ellen Papsch
2020-04-07 9:46 ` Ludovic Courtès
2020-04-07 11:34 ` Ellen Papsch
2020-04-07 20:19 ` Ludovic Courtès
2020-04-08 12:37 ` Ellen Papsch
2020-04-07 15:05 ` Alex Griffin
2020-04-07 16:47 ` Vagrant Cascadian
2020-04-08 12:25 ` Ellen Papsch
2020-04-08 15:07 ` Alex Griffin
2020-04-08 16:22 ` Vagrant Cascadian
2020-04-08 7:57 ` Pierre Neidhardt
2020-04-08 12:19 ` Alex Griffin
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=20200404101832.cmegsybfyrseazjq@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=ellen.papsch@wine-logistix.de \
--cc=guix-devel@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.
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).