From: Michal Ludvig <michal@logix.cz>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: PadLock XSHA
Date: Mon, 01 Sep 2008 13:32:48 +1200 [thread overview]
Message-ID: <48BB4640.1040407@logix.cz> (raw)
In-Reply-To: <20080831020941.GA25048@gondor.apana.org.au>
Herbert Xu wrote:
> On Sat, Aug 30, 2008 at 09:55:00PM +1200, Michal Ludvig wrote:
>> IIRC The first versions of VIA PadLock required the input data to be
>> aligned on 16-bytes boundaries and more importantly they always
>> finalised the hash. Therefore we had to collect all data before hashing
>> them.
>
> Hmm, the current manual states that it does a bswap on the input
> and therefore alignment isn't required. There is no mention about
> older processors requiring 16-byte alignment.
That's right, I confused SHA with AES in PadLock, sorry. With AES the
first versions required 16-byte alignment on input and output data as
well as on the control word and there's a flag in newer PadLocks that
allow doing AES on unaligned data.
>> AFAIK Recent versions of PadLock don't insist on finalising the hash and
>> don't insist on input data alignment either and this workaround isn't
>> needed anymore. I don't know if VIA still sells their motherboard models
>> with the older CPUs or not.
>
> Interesting. I couldn't find anything in the manual about not
> requireing finalisation. Do you know where I can find out more
> about this?
I can't find any PadLock guide newer than 2005-05-03 (probably the same
one that you have). I'll check with VIA what the status of this is.
Michal
next prev parent reply other threads:[~2008-09-01 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 8:43 PadLock XSHA Herbert Xu
2008-08-30 9:55 ` Michal Ludvig
2008-08-30 13:21 ` Herbert Xu
2008-08-31 2:09 ` Herbert Xu
2008-09-01 1:32 ` Michal Ludvig [this message]
2008-09-01 3:44 ` Herbert Xu
2008-10-01 23:48 ` Harald Welte
2008-10-01 23:45 ` Harald Welte
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=48BB4640.1040407@logix.cz \
--to=michal@logix.cz \
--cc=herbert@gondor.apana.org.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.