From: Milan Broz <mbroz@redhat.com>
To: Christoph Anton Mitterer
<christoph.anton.mitterer@physik.uni-muenchen.de>
Cc: dm-crypt@saout.de, Sven Eschenberg <sven@whgl.uni-frankfurt.de>
Subject: Re: [dm-crypt] crypsetup segfaulting during luksFormat
Date: Wed, 14 Jul 2010 20:24:32 +0200 [thread overview]
Message-ID: <4C3E00E0.8080902@redhat.com> (raw)
In-Reply-To: <1279131283.3270.108.camel@fermat.scientia.net>
On 07/14/2010 08:14 PM, Christoph Anton Mitterer wrote:
> For those people that did not hit the crash on luksFormat.... are they
> in trouble, too?
>
> E.g. by weak PBKDF2 derived keys or that like?
>
> Sven hinted that big endian systems might have even worse problems?
no. there is no bug at all with overflow or endianess, please read my replies.
(And I was not able reproduce it on Gentoo also, but I have slightly different
hardened config.)
Milan
next prev parent reply other threads:[~2010-07-14 18:24 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
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 [this message]
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=4C3E00E0.8080902@redhat.com \
--to=mbroz@redhat.com \
--cc=christoph.anton.mitterer@physik.uni-muenchen.de \
--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