public inbox for cryptsetup@lists.linux.dev
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: cryptsetup@lists.linux.dev
Subject: Re: cryptsetup LUKS: Too low iteration count: only 14
Date: Sat, 13 Aug 2022 18:48:27 +0200	[thread overview]
Message-ID: <20220813164827.GA7844@tansi.org> (raw)
In-Reply-To: <de150ba2-46fe-36f6-86b5-37411af760e6@gmail.com>

On Sat, Aug 13, 2022 at 18:11:48 CEST, Milan Broz wrote:
> On 13/08/2022 17:50, doffloster@gmail.com wrote:
> > Hi all,
> > 
> > I was playing around with LUKS extension in cryptsetup and noticed
> > that the iteration count was 14 in my case.
> > The iteration time that I chose (arbitrarily) is 4123ms which is above
> > 4 seconds!
> > So I was astonished to see an iteration count which is very low.
> > As far as I know, using a modern computer, the iteration count should
> > be above 100k.
> 
> Please do not confuse iteration for PBKDF2 (default in LUKS1) and
> memory-hard Argon2 KDF.
> 
> These are completely different algorithms, you cannot compare iteration
> costs here.
> 
> If you set 100k iteration with 1G memory cost for Argon2, you will get
> unlocking time that is perhaps in years... :-)

Argon2 operates on a completely different iteration scale than
PBKDF2 by a factor of 100'000 or so. 

A look into the documentation may help. If I remember correctly
the recommended minimal iteration count for Argon2 is 4.

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

  parent reply	other threads:[~2022-08-13 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-13 15:50 cryptsetup LUKS: Too low iteration count: only 14 doffloster
2022-08-13 16:11 ` Milan Broz
2022-08-13 16:24   ` Michael Kjörling
2022-08-13 16:48   ` Arno Wagner [this message]
2022-08-13 19:35   ` Michael Kjörling
2022-08-13 20:00     ` 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=20220813164827.GA7844@tansi.org \
    --to=arno@wagner.name \
    --cc=cryptsetup@lists.linux.dev \
    /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