From: Milan Broz <gmazyland@gmail.com>
To: j4ck32 <j4ck32@gmail.com>
Cc: cryptsetup@lists.linux.dev
Subject: Re: Unable to use a keyfile
Date: Sun, 12 Apr 2026 10:40:24 +0200 [thread overview]
Message-ID: <9855efa5-b11b-41bb-b6e9-74675011630f@gmail.com> (raw)
In-Reply-To: <CA+vw=VJc1Oh1v379uaJzSXPsfn_Mr5NmXFSwpaAOi0g+GMmS+A@mail.gmail.com>
On 4/12/26 10:09 AM, j4ck32 wrote:
> memtest86 immediately failed...
> I did multiple test runs and determined one of the two modules failed.
> So I removed the faulty module...
> Now my system accepts the original key-file again.
> And adding new key-files works again.
>
> Am Sa., 11. Apr. 2026 um 23:21 Uhr schrieb Milan Broz <gmazyland@gmail.com>:
>> This should work. Could you try to add "--pbkdf pbkdf2" for luksAddKey?
>
> I skipped that. Now that the issue is fixed.
>
> So using a key-file uses more memory than a passphrase?
No, a keyfile is processed the same way as passphrases.
But your previous passphrase (keyslot 0) used less memory.
With PBKDF2, the memory footprint is even smaller, just a few kilobytes.
It is only about probability & luck - passphrase could fail the same way.
Argon2 KDF is just a quite good memory pressure test :)
Milan
prev parent reply other threads:[~2026-04-12 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 18:50 Unable to use a keyfile j4ck32
2026-04-11 21:21 ` Milan Broz
2026-04-12 8:09 ` j4ck32
2026-04-12 8:40 ` Milan Broz [this message]
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=9855efa5-b11b-41bb-b6e9-74675011630f@gmail.com \
--to=gmazyland@gmail.com \
--cc=cryptsetup@lists.linux.dev \
--cc=j4ck32@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