public inbox for cryptsetup@lists.linux.dev
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: "Michael Kjörling" <michael@kjorling.se>, cryptsetup@lists.linux.dev
Subject: Re: cryptsetup LUKS: Too low iteration count: only 14
Date: Sat, 13 Aug 2022 22:00:15 +0200	[thread overview]
Message-ID: <df5fe77f-9474-6f8c-79cc-b199afbb7748@gmail.com> (raw)
In-Reply-To: <e05733d4-2e45-4075-b1cd-dadc753fb89e@home.arpa>

On 13/08/2022 21:35, Michael Kjörling wrote:
> On 13 Aug 2022 18:11 +0200, from gmazyland@gmail.com (Milan Broz):
>>> that the iteration count was 14 in my case.
>>> The iteration time that I chose (arbitrarily) is 4123ms
>>
>> If you set 100k iteration with 1G memory cost for Argon2, you will get
>> unlocking time that is perhaps in years... :-)
> 
> Out of curiosity, how did you arrive at the "years" order of
> magnitude? Is there an exponential component involved somewhere when
> increasing the iteration count?

Ah, my bad, sorry.
It was more a rhetoric note (I meant: it will take very long time.)

It expects that the memory cost is the same, though.
Once you will increase memory, it influences iteration time too.
Cryptsetup KDF benchmark tries to increase memory, then iterations,
but here it hits the 1G limit already.

Sorry for the confusion, I should be more exact :)
Milan

      reply	other threads:[~2022-08-13 20:00 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
2022-08-13 19:35   ` Michael Kjörling
2022-08-13 20:00     ` 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=df5fe77f-9474-6f8c-79cc-b199afbb7748@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=cryptsetup@lists.linux.dev \
    --cc=michael@kjorling.se \
    /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