[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190530023357.2mrjtslnka4i6dbl@gondor.apana.org.au>
Date: Thu, 30 May 2019 10:33:57 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Richard Weinberger <richard@....at>
Cc: linux-crypto@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-imx@....com,
festevam@...il.com, kernel@...gutronix.de, s.hauer@...gutronix.de,
shawnguo@...nel.org, davem@...emloft.net, david@...ma-star.at
Subject: Re: [RFC PATCH 1/2] crypto: Allow working with key references
On Thu, May 30, 2019 at 12:48:43AM +0200, Richard Weinberger wrote:
> Some crypto accelerators allow working with secure or hidden keys.
> This keys are not exposed to Linux nor main memory. To use them
> for a crypto operation they are referenced with a device specific id.
>
> This patch adds a new flag, CRYPTO_TFM_REQ_REF_KEY.
> If this flag is set, crypto drivers should tread the key as
> specified via setkey as reference and not as regular key.
> Since we reuse the key data structure such a reference is limited
> by the key size of the chiper and is chip specific.
>
> TODO: If the cipher implementation or the driver does not
> support reference keys, we need a way to detect this an fail
> upon setkey.
> How should the driver indicate that it supports this feature?
>
> Signed-off-by: Richard Weinberger <richard@....at>
We already have existing drivers doing this. Please have a look
at how they're doing it and use the same paradigm. You can grep
for paes under drivers/crypto.
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