[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y3cg0FjeO272ncFb@gondor.apana.org.au>
Date: Fri, 18 Nov 2022 14:06:08 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Nikolaus Voss <nikolaus.voss@...g-streit.com>
Cc: Horia Geanta <horia.geanta@....com>,
Pankaj Gupta <pankaj.gupta@....com>,
Gaurav Jain <gaurav.jain@....com>,
"David S. Miller" <davem@...emloft.net>,
Ahmad Fatoum <a.fatoum@...gutronix.de>,
David Gstir <david@...ma-star.at>,
Steffen Trumtrar <s.trumtrar@...gutronix.de>,
Nikolaus Voss <nv@...n.de>, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] crypto: caam: blob_gen.c: warn if key is insecure
On Mon, Nov 07, 2022 at 09:00:30AM +0100, Nikolaus Voss wrote:
> If CAAM is not in "trusted" or "secure" state, a fixed non-volatile key
> is used instead of the unique device key. This is the default mode of
> operation without secure boot (HAB). In this scenario, CAAM encrypted
> blobs should be used only for testing but not in a production
> environment, so issue a warning.
>
> Signed-off-by: Nikolaus Voss <nikolaus.voss@...g-streit.com>
>
> ---
> Changes
> =======
> v2: make warning more verbose, correct register, style fixes
>
> drivers/crypto/caam/blob_gen.c | 9 +++++++++
> drivers/crypto/caam/regs.h | 3 +++
> 2 files changed, 12 insertions(+)
This patch introduces a new warning with gcc or sparse using
C=1 W=1. Plesae fix.
Thanks,
--
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