From: Milan Broz <mbroz@redhat.com>
To: Tero Pesonen <dmcrypt-list@tpesonen.net>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Question on LUKS master key digest and its effect on security
Date: Tue, 22 Sep 2009 17:47:00 +0200 [thread overview]
Message-ID: <4AB8F174.2010800@redhat.com> (raw)
In-Reply-To: <200909221808.28418.dmcrypt-list@tpesonen.net>
Tero Pesonen wrote:
> Since there have been no comments on this, I was wondering if I should
> rather send questions of this sort on scri.crypt or some such place
> where these kind of topics are discussed? If so, is the iteration count
> 10 for the PBKDF2 correct? (So that I am able to formulate my question
> right and not pass on wrong information.)
Yes, 10 is currently hardcoded:
// Numbers of iterations for the master key digest
#define LUKS_MKD_ITER 10
If you need Clemens' formal LUKS specification it is here
http://cryptsetup.googlecode.com/svn-history/r42/wiki/LUKS-standard/on-disk-format.pdf
Please cc me if you receive analysis in reply, thanks.
(And btw independent code review to find possible implementation mistakes is
always welcomed too, mainly now after reimplementation PBKDF2 and AF to use
gcrypt and allowing other hash algorithms:-)
Milan
--
mbroz@redhat.com
next prev parent reply other threads:[~2009-09-22 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 17:39 [dm-crypt] Question on LUKS master key digest and its effect on security Tero Pesonen
2009-09-18 18:16 ` Milan Broz
2009-09-18 20:18 ` Tero Pesonen
2009-09-22 15:08 ` Tero Pesonen
2009-09-22 15:47 ` Milan Broz [this message]
2009-09-22 17:47 ` Tero Pesonen
2009-09-22 16:14 ` [dm-crypt] Question on LUKS master key digest and its effect on?security Heinz Diehl
2009-09-22 16:21 ` Milan Broz
2009-09-19 16:51 ` [dm-crypt] Question on LUKS master key digest and its effect on security Heinz Diehl
2009-09-19 19:00 ` Milan Broz
2009-09-20 11:28 ` Heinz Diehl
2009-09-20 15:09 ` Heinz Diehl
2009-09-20 18:11 ` Milan Broz
2009-09-20 21:03 ` Heinz Diehl
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=4AB8F174.2010800@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=dmcrypt-list@tpesonen.net \
/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