From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] question regarding Sha1 and 512 bit key xts mode
Date: Sun, 23 Aug 2015 21:38:59 +0200 [thread overview]
Message-ID: <20150823193859.GB15403@tansi.org> (raw)
In-Reply-To: <d6ed71a7ed7581214b7e3c67f8f5513b.squirrel@ssl.verfeiert.org>
On Sun, Aug 23, 2015 at 20:51:42 CEST, Sven Eschenberg wrote:
> On Sat, August 22, 2015 05:38, Heinz wrote:
> > Arno Wagner <arno@...> writes:
> >
> >> No, that is not the statement. The statement is that collision attacks
> >> (the SHA1-weakness) are irrelevant for password hasing.
> >
> > Or in other words, SHA1 is secure in this case. But why not always use the
> > best possible hash algorithm, instead of an option which is at least safe?
> > I would logically use always the strongest one, purely as a precaution,
> > and
> > not what has already demonstrated weaknesses of any kind. I would not want
> > to wait if SHA1 really holds a long time. :)
>
> Sorry to intervene here. Hashing in LUKS is only used to check if a
> password/passphrase is a candidate. So, even if you manage to find a
> collision, the worst that can happen is, that LUKS accepts the
> 'collisison' as valid key and you'll get gibberish on the mapping. Your
> encrypted data will be useless 'random' data and is not compromised then.
I seem to remember that PBKDF2 gets the hash discussed (SHA1) as input
and also that the AF splitter uses it. Still not an issue.
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
next prev parent reply other threads:[~2015-08-23 19:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 16:31 [dm-crypt] question regarding Sha1 and 512 bit key xts mode anderson jackson
2013-12-11 18:04 ` Arno Wagner
2015-08-22 3:38 ` Heinz
2015-08-22 10:04 ` Michael Kjörling
2015-08-22 14:05 ` Arno Wagner
2015-08-26 12:29 ` Heinz
2015-08-22 13:58 ` Arno Wagner
2015-08-26 12:51 ` Heinz
2015-08-23 18:51 ` Sven Eschenberg
2015-08-23 19:38 ` Arno Wagner [this message]
2015-08-23 20:21 ` Sven Eschenberg
2015-08-24 6:18 ` Milan Broz
2015-08-24 11:54 ` Arno Wagner
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=20150823193859.GB15403@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox