From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: Vagrant Cascadian <vagrant@debian.org>,
Felix Lechner <felix.lechner@lease-up.com>,
Guix Devel <guix-devel@gnu.org>, help-guix <help-guix@gnu.org>
Subject: Re: PSA for LUKS users
Date: Thu, 20 Apr 2023 11:32:46 +0200 [thread overview]
Message-ID: <7aee4c5d-662a-52fe-dbc3-7ba4893109ae@web.de> (raw)
In-Reply-To: <87edoftd1x.fsf@wireframe>
Am 20.04.23 um 06:03 schrieb Vagrant Cascadian:
> On 2023-04-19, Felix Lechner via wrote:
>> Given the broad popularity of LUKS full-disk encryption among our
>> fellow Guix users, I thought the community might appreciate reading
>> about potentially weak key-derivation functions in older LUKS
>> installations. [1]
>>
>> The article even offers fixes, although I cannot say whether your
>> system will boot after you follow the steps since I do not use LUKS
>> personally. Stay safe!
> ...
>> [1] https://mjg59.dreamwidth.org/66429.html
>
> In short, those instructions will almost certainly break Guix System!
Can confirm :) At least the described backup & restore procedure does work.
I also think, that our cryptsetup is quite old, so I built a patch for
updating: https://issues.guix.gnu.org/62960
> While recent grub2 finally has limited support for luks2, it only
> supports the weaker KDF (key derivation function) (PBKDF2?), as I
> understand it, though would be happy to be proven wrong!
The support seems pretty limited, as I only updated the LUKS version of
my root-partition to version 2 (still PBKDF) and it already refused to
boot...
~Jonathan
next prev parent reply other threads:[~2023-04-20 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 2:45 PSA for LUKS users Felix Lechner via
2023-04-20 4:03 ` Vagrant Cascadian
2023-04-20 9:32 ` Jonathan Brielmaier [this message]
2023-04-20 9:39 ` Attila Lendvai
2023-04-20 13:55 ` kiasoc5
2023-04-20 16:31 ` Josselin Poiret
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=7aee4c5d-662a-52fe-dbc3-7ba4893109ae@web.de \
--to=jonathan.brielmaier@web.de \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=vagrant@debian.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).