From: Stefan Hellermann <stefan@the2masters.de>
To: Sebastian Siewior <linux-crypto@ml.breakpoint.cc>
Cc: Herbert Xu <herbert@gondor.apana.org.au>, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] [crypto] XTS: use proper alignment.
Date: Wed, 05 Mar 2008 15:02:29 +0100 [thread overview]
Message-ID: <47CEA7F5.2080700@the2masters.de> (raw)
In-Reply-To: <20080305120153.GA18425@Chamillionaire.breakpoint.cc>
Sebastian Siewior schrieb:
> * Herbert Xu | 2008-03-05 19:52:03 [+0800]:
>
>> On Wed, Mar 05, 2008 at 12:46:52PM +0100, Sebastian Siewior wrote:
>>> I'm not sure if we are allowed to modify the IV or if it should
>>> remain untouched. If it is possible to modify it, I could encrypt it
>>> inplace and save two memcpy().
>>> I will check this tonight.
>> I just had a quick look and it seems that you should be able to
>> store the result in the IV.
> Okey,
>
>> However this won't work for LRW since we need the IV to increment
>> it. But then again LRW seems to be fine as it is since its
>> arguments are already aligned by the blkcipher walker.
> I just browsed LRW and it seems that it does not encrypt the IV at all.
>
> Stefan: Didn't you report that both, XTS and LRW are broken on your
> padlock? If so, could you please post the backtrace?
I think it crashed one time, but I haven't really tried using LRW since XTS is said to
provide better security. Now I'm not able to reproduce the crash, it works with vanilla
2.6.25-rc4.
I have other problems in 2.6.25-rc[1-3], I get segfaults every here and then. I tried
compiling gcc several time, 90% of the time it crashed somewhere. I have the feeling it
segfaults faster when I do the compile in a tmpfs-mounted directory. 2.6.24 works fine, I
haven't tested 2.6.25-rc4. I have to check my RAM, if it's good I will report this to LKML.
I think the LRW-crash I reported could be related to this.
Thanks
Stefan
PS: I'm away from Thursday 12:00 UTC till Tuesday.
>
>> Thanks,
>
> Sebastian
next prev parent reply other threads:[~2008-03-05 14:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 13:51 [PATCH] fix alignment problem in XTS and LRW blockmode Sebastian Siewior
2008-03-02 11:09 ` [PATCH] [crypto] XTS: use proper alignment Sebastian Siewior
2008-03-02 13:35 ` [PATCH] [PATCH] [crypto] LRW: " Sebastian Siewior
2008-03-02 14:01 ` Stefan Hellermann
2008-03-02 16:23 ` Herbert Xu
2008-03-05 11:17 ` Herbert Xu
2008-03-05 11:16 ` [PATCH] [crypto] XTS: " Herbert Xu
2008-03-05 11:46 ` Sebastian Siewior
2008-03-05 11:52 ` Herbert Xu
2008-03-05 12:01 ` Sebastian Siewior
2008-03-05 14:02 ` Stefan Hellermann [this message]
2008-03-05 16:37 ` Sebastian Siewior
2008-03-05 22:17 ` [PATCH] [crypto] XTS: use proper alignment v2 Sebastian Siewior
2008-03-05 22:48 ` Stefan Hellermann
2008-03-06 8:52 ` Sebastian Siewior
2008-03-06 10:53 ` Stefan Hellermann
2008-03-06 10:57 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2008-02-24 11:01 [RFC] padlock aes, unification of setkey() Sebastian Siewior
2008-02-24 11:54 ` Stefan Hellermann
2008-02-24 12:51 ` Sebastian Siewior
2008-02-24 20:07 ` Via Padlock Bug with LRW/XTS Stefan Hellermann
2008-03-02 11:20 ` [PATCH] [crypto] XTS: use proper alignment Sebastian Siewior
2008-03-02 12:04 ` Stefan Hellermann
2008-03-02 13:22 ` Sebastian Siewior
2008-03-02 13:49 ` Stefan Hellermann
2008-03-02 14:04 ` Stefan Hellermann
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=47CEA7F5.2080700@the2masters.de \
--to=stefan@the2masters.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@ml.breakpoint.cc \
--cc=linux-crypto@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).