From: Milan Broz <mbroz@redhat.com>
To: Sven Eschenberg <sven@whgl.uni-frankfurt.de>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] crypsetup segfaulting during luksFormat
Date: Thu, 08 Jul 2010 17:11:08 +0200 [thread overview]
Message-ID: <4C35EA8C.9060206@redhat.com> (raw)
In-Reply-To: <1278599384.3147.67.camel@Koma-Station.localdomain>
On 07/08/2010 04:29 PM, Sven Eschenberg wrote:
> Hi Milan,
>
> Even worse, actually byte swappig is done to store the int in a big
> endian manner, unfortunately, since it is done wrong, on big endian
> systems all block indeces would be zero and they are part of the Derived
> Key. I wonder if this has a security impact as in quality of derived key
> on big endian systems.
You mean when int is big endian and 64bit? Do you see system where it is wrong
or just guessing?
There is no direct key encryption derived using this code, it is just keyslot
obfuscation + keyslot passphrase verification (master key in LUKS is generated from RNG)
(plain crypt do not use this at all)
That algorithm is not new and passed PBKDF2 test vectors (I will probably add this test
to api check also).
I run test on several architectures - all keyslot operation should fail on prepared image
if there is such bug.
(But it should explicitly use uint32 there.)
Milan
next prev parent reply other threads:[~2010-07-08 15:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 17:19 [dm-crypt] crypsetup segfaulting during luksFormat Sven Eschenberg
2010-07-07 17:36 ` Arno Wagner
2010-07-07 17:49 ` Sven Eschenberg
2010-07-07 20:19 ` Arno Wagner
2010-07-07 20:44 ` Milan Broz
2010-07-07 20:58 ` Sven Eschenberg
2010-07-07 21:22 ` Milan Broz
2010-07-08 2:22 ` Sven Eschenberg
2010-07-08 9:30 ` Arno Wagner
2010-07-08 13:37 ` Sven Eschenberg
2010-07-08 14:16 ` Milan Broz
2010-07-08 14:29 ` Sven Eschenberg
2010-07-08 15:11 ` Milan Broz [this message]
2010-07-08 18:44 ` Sven Eschenberg
2010-07-09 7:22 ` Milan Broz
2010-07-09 12:18 ` Sven Eschenberg
2010-07-09 12:46 ` Milan Broz
2010-07-14 18:14 ` Christoph Anton Mitterer
2010-07-14 18:24 ` Milan Broz
2010-07-14 18:56 ` Sven Eschenberg
2010-07-07 21:40 ` Milan Broz
2010-07-07 22:00 ` Arno Wagner
2010-07-08 2:13 ` Sven Eschenberg
2010-07-07 20:51 ` Arno Wagner
2010-07-07 18:36 ` Milan Broz
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=4C35EA8C.9060206@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=sven@whgl.uni-frankfurt.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