From: Herbert Xu <herbert@gondor.apana.org.au>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: "Horia Geantă" <horia.geanta@nxp.com>,
"Pankaj Gupta" <pankaj.gupta@nxp.com>,
"Gaurav Jain" <gaurav.jain@nxp.com>,
"David S. Miller" <davem@davemloft.net>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
stable@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] crypto: caam - use print_hex_dump_devel to guard key hex dumps
Date: Tue, 5 May 2026 17:28:43 +0800 [thread overview]
Message-ID: <afm4S8FhUTli5Sc5@gondor.apana.org.au> (raw)
In-Reply-To: <20260427163937.337966-3-thorsten.blum@linux.dev>
On Mon, Apr 27, 2026 at 06:39:37PM +0200, Thorsten Blum wrote:
> Use print_hex_dump_devel() for dumping sensitive key material in
> *_setkey() and gen_split_key() to avoid leaking secrets at runtime when
> CONFIG_DYNAMIC_DEBUG is enabled.
>
> Fixes: 6e005503199b ("crypto: caam - print debug messages at debug level")
> Cc: stable@vger.kernel.org
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> drivers/crypto/caam/caamalg.c | 12 ++++++------
> drivers/crypto/caam/caamalg_qi.c | 12 ++++++------
> drivers/crypto/caam/caamhash.c | 4 ++--
> drivers/crypto/caam/key_gen.c | 4 ++--
> 4 files changed, 16 insertions(+), 16 deletions(-)
All applied. Thanks.
--
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
prev parent reply other threads:[~2026-05-05 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 16:39 [PATCH 1/2] crypto: caam - use print_hex_dump_devel to guard key hex dumps Thorsten Blum
2026-04-27 16:39 ` [PATCH 2/2] " Thorsten Blum
2026-05-05 9:28 ` Herbert Xu [this message]
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=afm4S8FhUTli5Sc5@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=gaurav.jain@nxp.com \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=stable@vger.kernel.org \
--cc=thorsten.blum@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox