public inbox for cryptsetup@lists.linux.dev
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: Ondrej Kozina <okozina@redhat.com>
Cc: cryptsetup@lists.linux.dev, Lamy Geier <lamyergeier@gmail.com>
Subject: Re: Slow unlock of the LUKS device at boot
Date: Thu, 1 Dec 2022 22:07:22 +0100	[thread overview]
Message-ID: <20221201210722.GA29541@tansi.org> (raw)
In-Reply-To: <28ce5fe7-89c3-7548-d8e8-71c830f25711@redhat.com>

On Thu, Dec 01, 2022 at 15:40:15 CET, Ondrej Kozina wrote:
> On 29. 11. 22 20:50, Lamy Geier wrote:
[...]
> > Keyslots:
> >     0: luks2
> >           Key:        512 bits
> >           Priority:   normal
> >           Cipher:     aes-xts-plain64
> >           Cipher key: 512 bits
> >           PBKDF:      argon2id
> >           Time cost:  1000
>                         ^^^^
> This is insane value for argon2 and it would explain your 6 minutes unlock
> time. Usually on my 2 years old laptop I get values in range 6-9 iterations
> (Time cost) with 4 threads and 1GiB ram used when I let cryptsetup do the
> benchmark with default target time ~2 seconds. Are you sure you did not add
> --pbkdf-force-iterations parameter in your luksAddKey command earlier?
> 
> With regards
> O.

That seems to be it. So misconfiguration after all as I suspected.

Regards,
Arno 

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

      reply	other threads:[~2022-12-01 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 19:50 Slow unlock of the LUKS device at boot Lamy Geier
2022-11-29 20:02 ` Lamy Geier
2022-11-29 20:19 ` Lamy Geier
2022-11-29 20:39   ` Arno Wagner
2022-12-01 14:40 ` Ondrej Kozina
2022-12-01 21:07   ` Arno Wagner [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=20221201210722.GA29541@tansi.org \
    --to=arno@wagner.name \
    --cc=cryptsetup@lists.linux.dev \
    --cc=lamyergeier@gmail.com \
    --cc=okozina@redhat.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