From: Herbert Xu <herbert@gondor.apana.org.au>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Will Deacon <will.deacon@arm.com>,
Nicolas Pitre <nico@linaro.org>
Subject: Re: [RFC PATCH] arm64: add support for AES in CCM mode using Crypto Extensions
Date: Tue, 25 Feb 2014 17:08:35 +0800 [thread overview]
Message-ID: <20140225090835.GA11135@gondor.apana.org.au> (raw)
In-Reply-To: <CAKv+Gu_A_04P=nOoPfxhJMC3bbEPTcpgZO0Ldw2H4BV7T_gTbw@mail.gmail.com>
On Tue, Feb 25, 2014 at 08:21:22AM +0100, Ard Biesheuvel wrote:
>
> For the authenticate-only data, this is manageable as you are only
> dealing with input, but when dealing with both in- and output, as in
> the core of CCM, it becomes very tedious.
> So instead, I have opted for an inner blkcipher instance which takes
> care of all of that. Could you suggest another approach that if
> preferable?
I don't think the walk helper actually needs the tfm apart from
getting a couple of parameters out of it, so perhaps we can just
change the helper to not depend on a tfm.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
WARNING: multiple messages have this Message-ID (diff)
From: herbert@gondor.apana.org.au (Herbert Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] arm64: add support for AES in CCM mode using Crypto Extensions
Date: Tue, 25 Feb 2014 17:08:35 +0800 [thread overview]
Message-ID: <20140225090835.GA11135@gondor.apana.org.au> (raw)
In-Reply-To: <CAKv+Gu_A_04P=nOoPfxhJMC3bbEPTcpgZO0Ldw2H4BV7T_gTbw@mail.gmail.com>
On Tue, Feb 25, 2014 at 08:21:22AM +0100, Ard Biesheuvel wrote:
>
> For the authenticate-only data, this is manageable as you are only
> dealing with input, but when dealing with both in- and output, as in
> the core of CCM, it becomes very tedious.
> So instead, I have opted for an inner blkcipher instance which takes
> care of all of that. Could you suggest another approach that if
> preferable?
I don't think the walk helper actually needs the tfm apart from
getting a couple of parameters out of it, so perhaps we can just
change the helper to not depend on a tfm.
Cheers,
--
Email: Herbert Xu <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:[~2014-02-25 9:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 8:21 [RFC PATCH] arm64: add support for AES in CCM mode using Crypto Extensions Ard Biesheuvel
2014-02-11 8:21 ` Ard Biesheuvel
2014-02-25 7:02 ` Herbert Xu
2014-02-25 7:02 ` Herbert Xu
2014-02-25 7:12 ` Ard Biesheuvel
2014-02-25 7:12 ` Ard Biesheuvel
2014-02-25 7:16 ` Herbert Xu
2014-02-25 7:16 ` Herbert Xu
2014-02-25 7:21 ` Ard Biesheuvel
2014-02-25 7:21 ` Ard Biesheuvel
2014-02-25 9:08 ` Herbert Xu [this message]
2014-02-25 9:08 ` Herbert Xu
2014-02-25 10:11 ` Ard Biesheuvel
2014-02-25 10:11 ` Ard Biesheuvel
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=20140225090835.GA11135@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=ard.biesheuvel@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=nico@linaro.org \
--cc=will.deacon@arm.com \
/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.