From: Andreas Heinlein <aheinlein@gmx.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] Performance/Requirements of Argon2 header with removable devices
Date: Fri, 11 Jun 2021 10:08:31 +0200 [thread overview]
Message-ID: <416615b9-ac00-036c-ae00-7b3e91a22aff@gmx.com> (raw)
Hello,
I have another question regarding the new LUKS2 header resp. the Argon2 algorithm.
I understand that Argon2 deliberately requires a large amount of memory, and that this amount is dynamically calculated when creating the device.
How does a removable device encrypted with LUKS behave in this case? If I create the device on i.e. a Core i9 with 16 GiB RAM and then try to open it on an Atom x5 with 1GiB, will this be possible at all? Yes, it would be ultra-slow in any case even with LUKS1 header, because of the number of iterations, but it would work.
Thanks,
Andreas
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de
next reply other threads:[~2021-06-11 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 8:08 Andreas Heinlein [this message]
2021-06-11 8:34 ` [dm-crypt] Re: Performance/Requirements of Argon2 header with removable devices Arno Wagner
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=416615b9-ac00-036c-ae00-7b3e91a22aff@gmx.com \
--to=aheinlein@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).