All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Dmitry <dimanne@gmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] Argon2 limits choice
Date: Sun, 3 Oct 2021 23:30:13 +0100	[thread overview]
Message-ID: <CAC9D8R6jHQr_fKco1PjGvcJg8rLxHFrPNGxBiNzncj5sONJcWg@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 686 bytes --]

Hi,

I am wondering if there are objective reasons for such conservative ***upper**
**hard** limits* for Argon?

} else if (!strcmp(kdf, "argon2i") || !strcmp(kdf, "argon2id")) {
   limits->max_iterations = UINT32_MAX;
   limits->max_memory     = 4*1024*1024; /* 4GiB */
   limits->max_parallel   = 4;
}

(well, apart from UINT32_MAX, which makes sense, kind of)

Just to reiterate, I am not talking about minimum values, or default
values. The question is about *upper limits*.

P.S.
I was personally thinking about using ~32 threads and ~128GiB of RAM as KDF
parameters...


-- 
Dmitry
*Sent from my gmail*
GPG/PGP Key fingerprint = 1670 0E8A 4AEC 179D 326F  BECE 8B33 360D 8717 9711

[-- Attachment #1.2: Type: text/html, Size: 1336 bytes --]

[-- Attachment #2: Type: text/plain, Size: 147 bytes --]

_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de

             reply	other threads:[~2021-10-04  0:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03 22:30 Dmitry Dmitry [this message]
2021-10-04  0:28 ` [dm-crypt] Re: Argon2 limits choice Arno Wagner
2021-10-04  6:25 ` Milan Broz
2021-10-04  6:29   ` Dmitry Dmitry

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=CAC9D8R6jHQr_fKco1PjGvcJg8rLxHFrPNGxBiNzncj5sONJcWg@mail.gmail.com \
    --to=dimanne@gmail.com \
    --cc=dm-crypt@saout.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.