From: Segher Boessenkool <segher@kernel•crashing.org>
To: David Laight <David.Laight@ACULAB•COM>
Cc: "linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
'Markus Stockhausen' <stockhausen@collogia•de>,
"linux-crypto@vger•kernel.org" <linux-crypto@vger•kernel.org>
Subject: Re: [PATCH v1 2/7] AES for PPC/SPE - aes tables
Date: Mon, 16 Feb 2015 08:37:06 -0600 [thread overview]
Message-ID: <20150216143706.GA3609@gate.crashing.org> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1CAE46B2@AcuExch.aculab.com>
On Mon, Feb 16, 2015 at 02:19:50PM +0000, David Laight wrote:
> From: Markus Stockhausen
> > 4K AES tables for big endian
>
> I can't help feeling that you could give more information about how the
> values are generated.
... and an explanation of why this does not open you up to a timing attack?
Segher
next prev parent reply other threads:[~2015-02-16 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 12:45 [PATCH v1 2/7] AES for PPC/SPE - aes tables Markus Stockhausen
2015-02-16 14:19 ` David Laight
2015-02-16 14:37 ` Segher Boessenkool [this message]
2015-02-16 17:18 ` AW: " Markus Stockhausen
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=20150216143706.GA3609@gate.crashing.org \
--to=segher@kernel$(echo .)crashing.org \
--cc=David.Laight@ACULAB$(echo .)COM \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=stockhausen@collogia$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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