Cryptsetup development
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: "Lars Francke" <lars.francke@gmail.com>,
	"Michael Kjörling" <152cc69a347e@ewoof.net>
Cc: cryptsetup@lists.linux.dev
Subject: Re: cryptsetup - No key available with passphrase
Date: Fri, 3 Mar 2023 08:55:50 +0100	[thread overview]
Message-ID: <47da0423-7e8c-c059-c65c-fe6252b0e384@gmail.com> (raw)
In-Reply-To: <CAD-Ua_gQLB+6a8=eRQd7B8u76hmvGFH+xPtzJKXPwn=gjuF=uw@mail.gmail.com>

Hi,

On 3/2/23 23:12, Lars Francke wrote:
> Thank you both for your help and sorry for raising this unrelated
> issue - cryptsetup was probably just so early in the installation
> phase, other steps would probably have failed later as well.
> I can't think of anything cryptsetup could  have done to prevent this.

It is related - as it is definitely only you who experienced it.

Actually it is quite interesting issue. Argon2 KDF uses a lot of memory
and any glitch (even one bit flip) will change it's output.
So memory failure explains what you see here.
(You should see this rarely if --type luks1 was used for format,
as LUKS1 does not use Argon2. But memory failure is just a recipe
for disaster later...)

Thanks,
Milan

  reply	other threads:[~2023-03-03  7:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 14:03 cryptsetup - No key available with passphrase Lars Francke
2023-03-02 15:01 ` Milan Broz
2023-03-02 16:23   ` Lars Francke
2023-03-02 16:40     ` Milan Broz
2023-03-02 20:34       ` Lars Francke
2023-03-02 21:46         ` Michael Kjörling
2023-03-02 22:12           ` Lars Francke
2023-03-03  7:55             ` Milan Broz [this message]
2023-03-03 10:17               ` Michael Kjörling
2023-03-03 17:42               ` Arno Wagner
2023-03-04  6:54                 ` Lars Francke

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=47da0423-7e8c-c059-c65c-fe6252b0e384@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=152cc69a347e@ewoof.net \
    --cc=cryptsetup@lists.linux.dev \
    --cc=lars.francke@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