[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200716121932.GA31870@gondor.apana.org.au>
Date: Thu, 16 Jul 2020 22:19:32 +1000
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Horia Geantă <horia.geanta@....com>
Cc: Iuliana Prodan <iuliana.prodan@....com>,
Aymen Sghaier <aymen.sghaier@....com>,
"David S. Miller" <davem@...emloft.net>,
Silvano Di Ninno <silvano.dininno@....com>,
Franck Lenormand <franck.lenormand@....com>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>
Subject: Re: [PATCH 2/2] crypto: caam - support tagged keys for skcipher
algorithms
On Thu, Jul 16, 2020 at 03:07:50PM +0300, Horia Geantă wrote:
>
> So instead of tk(cbc(aes)) use paes(cbc(aes) or cbc(paes)?
Well if we're following the existing paes model then it'd be
cbc(paes).
> How would this work for hmac(sha512),
> paes(hmac(sha512)) or hmac(psha512), or even phmac(sha512)?
Perhaps hmac(psha512).
The point is whatever scheme you come up with has to be consistent
across all drivers.
Cheers,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists