From: Herbert Xu <herbert@gondor.apana.org.au>
To: Michael Heyse <mhk@designassembly.de>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: which one is broken: VIA padlock aes or aes_i586?
Date: Wed, 22 Feb 2006 12:31:37 +1100 [thread overview]
Message-ID: <20060222013137.GA844@gondor.apana.org.au> (raw)
In-Reply-To: <43FB0746.5010200@designassembly.de>
On Tue, Feb 21, 2006 at 01:27:50PM +0100, Michael Heyse wrote:
>
> after upgrading the kernel from 2.6.12.5 to 2.6.16-rc4, decryption of my disk fails. As I am using the Nehemia's Padlock and aes-cbc-essiv, I guess this is the reason:
>
> (from ChangeLog-2.6.13)
> commit 476df259cd577e20379b02a7f7ffd086ea925a83
> Author: Herbert Xu <herbert@gondor.apana.org.au>
> Date: Wed Jul 6 13:54:09 2005 -0700
>
> [CRYPTO] Update IV correctly for Padlock CBC encryption
>
> When the Padlock does CBC encryption, the memory pointed to by EAX is
> not updated at all. Instead, it updates the value of EAX by pointing
> it to the last block in the output. Therefore to maintain the correct
> semantics we need to copy the IV.
I don't think this patch is your problem since it's part of the multiblock
code which doesn't exist in 2.6.12 at all. Of course the multiblock code
itself could be buggy. I'll take a look.
Thanks,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2006-02-22 1:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 12:27 Michael Heyse
2006-02-22 1:31 ` Herbert Xu [this message]
2006-02-22 11:45 ` Herbert Xu
2006-02-22 12:05 ` Michael Heyse
2006-02-22 12:32 ` [SOLVED] " Michael Heyse
2006-02-22 12:43 ` Herbert Xu
2006-02-22 11:49 ` Michael Heyse
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=20060222013137.GA844@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mhk@designassembly.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
all inboxes | Powered by JetHome®