From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] different default key sizes for CREATE and LUKSFORMAT
Date: Thu, 19 Nov 2009 13:24:45 +0100 [thread overview]
Message-ID: <20091119122445.GA10856@tansi.org> (raw)
In-Reply-To: <20091119092107.GA7875@fancy-poultry.org>
On Thu, Nov 19, 2009 at 10:21:07AM +0100, Heinz Diehl wrote:
> On 19.11.2009, Arno Wagner wrote:
>
> > If I understand this correctly, this is the "iteration-count"
> > parameter to PBKDF2. If so, then RFC 2898 recommends a minimum
> > count of 1000 anyways.
>
> This has been discussed in various places, and the conclusion was that it
> should not be lower than 50.000 iterations. See f.ex. rfc3962 on
> implemetation of PBKDF2 for Kerberos5.
>
> > The main purpose of this parameter is to make exhaustive search more expensive.
>
> Yes, it should make bruteforcing a lot more time-expensive.
>
> > I think this should definitely go up to 1000.
>
> I think this should maybe go up to 50.000 or 100.000.
> If I understood all correctly, so should a bump-up to 100.000 not have
> much noticeable impact on the main speed either.
>
> Please correct me if I'm wrong.
Just did a few benchmarks with a 10MB loopback on a dual
Athlon 64 5600+. As the master key iterations are not accessible
via commandline, I have tried some time settings for the
slot key (-i <milisec>). They should have similar effort.
Iteration time Iterations time (elapsed) for luksOpen
1 ms 301 1.01 sec
10 ms 3 029 1.01 sec
100 ms 30 247 1.06 sec
1 sec 303 694 1.51 sec
10 sec 3 043 420 6.02 sec
100 sec 30 212 200 50.92 sec
Ok, something is going on, that should be > 100 sec on the
last one. Nonetheless a rough estimation is possible. Maybe
a cache issue.
I would estimate that the time for 100'000 iterations is below
1 sec even for weak systems. For mine it is around 0.15 sec.
This makes going to 100'000 on mk_iter entirely feasible.
I curretntly do not see whether this is really needed, but
clearly it is not a problem and 100'000 is the recommended
value, so let's use it. Anybody having real slowdown because
they run this on a 25 Mhz 386SX CPU can still reduce the
count via commandline.
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
next prev parent reply other threads:[~2009-11-19 12:24 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 [this message]
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
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=20091119122445.GA10856@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.