From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] different default key sizes for CREATE and LUKSFORMAT
Date: Wed, 18 Nov 2009 14:26:10 +0100 [thread overview]
Message-ID: <4B03F5F2.9080609@redhat.com> (raw)
In-Reply-To: <4B03D865.8070905@redhat.com>
On 11/18/2009 12:20 PM, Milan Broz wrote:
> For default LUKS header hash:
>
> - default is SHA1
>
> switching to another (probably SHA-256?) means complete incompatibility
> with all cryptsetup <1.1.x, this need some time when all most distros
> use new cryptsetup.
> No need to hurry, there is no problem with SHA1 in this application
> of hash function.
Also I think we can increase MK digest iterations
(default is now 10, increasing it to 1000 should not cause any performance
problems. Just make the possible attack to MK digest more complicated
if some hash is completely broken in future.)
Does this make sense of it is not needed?
Milan
next prev parent reply other threads:[~2009-11-18 13:26 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 [this message]
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
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=4B03F5F2.9080609@redhat.com \
--to=mbroz@redhat.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 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.