From: Milan Broz <gmazyland@gmail.com>
To: j4ck32 <j4ck32@gmail.com>, cryptsetup@lists.linux.dev
Subject: Re: Unable to use a keyfile
Date: Sat, 11 Apr 2026 23:21:43 +0200 [thread overview]
Message-ID: <42b530ab-3f92-4aae-9714-076dbccaf0f0@gmail.com> (raw)
In-Reply-To: <CA+vw=V+c4SP+dPwY6oYk=V+QQS=797XuqSRan8N5vSSFwvN8aw@mail.gmail.com>
On 4/11/26 8:50 PM, j4ck32 wrote:
> Hello,
>
> I have a strange problem with my LUKS setup.
>
> I can successfully add a keyfile to my LUKS container, but when I try
> to open the container with it the keyfile is rejected.
> I made many attempts with different iterations, but the result is
> always the same.
This should work. Could you try to add "--pbkdf pbkdf2" for luksAddKey?
This will use old PBKDF2 (as in LUKS1) for keyslots.
If it works, I strongly suspect you have issues with hardware.
Specifically if you say "sometimes it works" - this must work always,
it is a deterministic algorithm.
I have seen this several times (note new keyslot use a lot of more memory
that could trigger the issue).
Milan
next prev parent reply other threads:[~2026-04-11 21:21 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 [this message]
2026-04-12 8:09 ` j4ck32
2026-04-12 8:40 ` Milan Broz
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=42b530ab-3f92-4aae-9714-076dbccaf0f0@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