All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Add --iter-count in order to not use --iter-time
Date: Wed, 20 Sep 2017 12:15:54 +0200	[thread overview]
Message-ID: <20170920101554.GA12152@tansi.org> (raw)
In-Reply-To: <2fe51fae-d167-da2f-557c-7ec9c417bd9f@gmail.com>


On Wed, Sep 20, 2017 at 00:40:22 CEST, Milan Broz wrote:
[...]
> 
> This option can be quite dangerous but I agree that there is a use case
> for it.
> 

I agree that while this option will allow some people to shoot 
themselves in the foot (and hence is somewhat dangerous), it
does have its uses. Unfortunately, people can always abotage 
themselves when using crypto, so I think the additional risk is
small.

One thing to think about with the memory hard KDF for LUKS2 
(I assume Argon2) is whether to give the user access to all 
the relevant parameters. I think the same reasoning as to 
BPKDF2 iterations applies, i.e. warn people to not do this 
unless they know what they are doing, but if they want to 
do it anywys, give them a clean way to do so to minimize
additional risks.

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:[~2017-09-20 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7fe591c8-0e75-f0c9-6ba2-1e4a2f85caca@bitmessage.ch>
2017-09-19 20:43 ` [dm-crypt] Add --iter-count in order to not use --iter-time Oliver Smith
2017-09-19 22:40   ` Milan Broz
2017-09-20 10:15     ` 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=20170920101554.GA12152@tansi.org \
    --to=arno@wagner.name \
    --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.