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] different default key sizes for CREATE and	LUKSFORMAT
Date: Sat, 21 Nov 2009 11:47:32 +0100	[thread overview]
Message-ID: <20091121104732.GA560@tansi.org> (raw)
In-Reply-To: <4B068840.6070508@redhat.com>

On Fri, Nov 20, 2009 at 01:14:56PM +0100, Milan Broz wrote:
> On 11/19/2009 02:00 PM, Heinz Diehl wrote:
> > On 19.11.2009, Arno Wagner wrote: 
> > 
> >> Anybody having real slowdown because they run this 
> >> on a 25 Mhz 386SX CPU can still reduce the count via commandline.
> > 
> > I'm afraid there is no commandline option to change that. "--iter-time" is 
> > related to the iterations of the passphrase, not the MK.
> 
> yes but I do not want add another iteration option, too confusing to users.
> 
> What about derive the MK digest iteration count from calculated keyslot
> iteration time (I suggest 1/5 of calculated time) - so for default 1 second
> it is cca 200ms - not accurate, because benchmark uses different message on input)
> but with minimum 1000 iterations?
> 
> (on my quite slow testing VM it is cca 20000 iterations)
> 
> This should be enough.
> This will add maximum 1.6 second processing time if all 8 slots is used,
> so it is acceptable but also provides needed slow-down for brute force.
> 
> Milan

Good idea, I like it. However use the same time as for the keyslots.
There is really no reason to have one use less iterations than
the other. 

The two iterations are linked security-wise, so treating them the same
makes sense.

Incidentially, it should only add the time once, there is only
one Master Key. 

Arno
-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

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:[~2009-11-21 10:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 22:45 [dm-crypt] different default key sizes for CREATE and LUKSFORMAT Stefan Xenon
2009-11-18  5:45 ` Arno Wagner
2009-11-18 10:01   ` Stefan Xenon
2009-11-18 10:25     ` Arno Wagner
2009-11-18 11:20       ` Milan Broz
2009-11-18 13:26         ` Milan Broz
2009-11-18 15:17           ` Heinz Diehl
2009-11-19  7:41           ` Arno Wagner
2009-11-19  9:21             ` Heinz Diehl
2009-11-19 12:24               ` Arno Wagner
2009-11-19 12:28                 ` Arno Wagner
2009-11-19 13:00                 ` Heinz Diehl
2009-11-20 12:14                   ` Milan Broz
2009-11-20 15:43                     ` Heinz Diehl
2009-11-21 10:47                     ` Arno Wagner [this message]
2009-11-21 12:40                       ` Stefan Xenon
2009-11-21 17:26                         ` Arno Wagner
2009-11-19 20:00                 ` Stefan Xenon
2009-11-20 12:22                   ` Milan Broz
2009-11-23 13:45             ` Roscoe
2009-11-23 14:29               ` Milan Broz
2009-11-23 15:46                 ` Arno Wagner
2009-11-23 16:05                 ` Heinz Diehl
2009-11-19  7:28         ` Arno Wagner
2009-11-20 12:43         ` Jonas Meurer

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=20091121104732.GA560@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.