From: Stephan Mueller <smueller@chronox.de>
To: Atul Gupta <atul.gupta@chelsio.com>
Cc: "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"davejwatson@fb.com" <davejwatson@fb.com>,
Ganesh GR <ganeshgr@chelsio.com>, Harsh Jain <Harsh@chelsio.com>
Subject: Re: [crypto 6/8] chtls: TCB and Key program
Date: Thu, 07 Dec 2017 16:27:39 +0100 [thread overview]
Message-ID: <2747471.DjaIqLtZ2I@tauon.chronox.de> (raw)
In-Reply-To: <MWHPR1201MB0238C75889F4E986F338B05297330@MWHPR1201MB0238.namprd12.prod.outlook.com>
Am Donnerstag, 7. Dezember 2017, 16:08:04 CET schrieb Atul Gupta:
Hi Atul,
> > As far as I see, the key is part of the skb (via kctx). This skb is
> > released after being processed. The release calls kfree_skb which does
> > not zeroize the key. Wouldn't it make sense to clear the memory of the
> > key when the skb is released? [Atul] we should perhaps memset the info
> > received from user so that driver has no info on key once its written on
> > chip memory. memset(gcm_ctx->key, 0, keylen);
>
> Are you saying that the skb (via kctx) above does not obtain a copy of the
> key? If not, what is done in chtls_key_info? It does have a key copy, I was
> not sure how key info is accessed once skb is released.
All I am saying is that this key copy should be zapped when the memory is
released. Thus, if the skb has a copy of the key, at least at the time of
free() of the skb, a memset() of the key memory should be done (or before).
>
>
> Ciao
> Stephan
>
> Thanks
> Atul
Ciao
Stephan
prev parent reply other threads:[~2017-12-07 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 11:40 [crypto 6/8] chtls: TCB and Key program Atul Gupta
2017-12-05 13:06 ` Stephan Mueller
2017-12-07 14:21 ` Atul Gupta
2017-12-07 14:42 ` Stephan Mueller
2017-12-07 15:08 ` Atul Gupta
2017-12-07 15:27 ` Stephan Mueller [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=2747471.DjaIqLtZ2I@tauon.chronox.de \
--to=smueller@chronox.de \
--cc=Harsh@chelsio.com \
--cc=atul.gupta@chelsio.com \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=ganeshgr@chelsio.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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