> -----Original Message-----
> From: linux-crypto-ow...@vger.kernel.org <linux-crypto-ow...@vger.kernel.org> 
> On Behalf Of Herbert Xu
> Sent: Thursday, July 16, 2020 2:20 PM
> To: Horia Geantă <horia.gea...@nxp.com>
> Cc: Iuliana Prodan <iuliana.pro...@nxp.com>; Aymen Sghaier 
> <aymen.sgha...@nxp.com>; David S. Miller <da...@davemloft.net>;
> Silvano Di Ninno <silvano.dini...@nxp.com>; Franck Lenormand 
> <franck.lenorm...@nxp.com>; linux-cry...@vger.kernel.org;
> linux-kernel@vger.kernel.org; dl-linux-imx <linux-...@nxp.com>
> Subject: Re: [PATCH 2/2] crypto: caam - support tagged keys for skcipher 
> algorithms
>
> <<< External Email >>>
> 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).
>
That would make no sense though, as sha512 does not involve any keys ...
It's the HMAC part that needs the keys. So phmac(sha512) then?

> The point is whatever scheme you come up with has to be consistent
> across all drivers.
>
> Cheers,
> --
> Email: Herbert Xu <herb...@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Pascal van Leeuwen
Silicon IP Architect Multi-Protocol Engines, Rambus Security
Rambus ROTW Holding BV
+31-73 6581953

Note: The Inside Secure/Verimatrix Silicon IP team was recently acquired by 
Rambus.
Please be so kind to update your e-mail address book with my new e-mail address.


** This message and any attachments are for the sole use of the intended 
recipient(s). It may contain information that is confidential and privileged. 
If you are not the intended recipient of this message, you are prohibited from 
printing, copying, forwarding or saving it. Please delete the message and 
attachments and notify the sender immediately. **

Rambus Inc.<http://www.rambus.com>

Reply via email to