From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ivy Lopez <skunkolee@gmail.com>, peterhuewe@gmx.de, jarkko@kernel.org
Cc: jgg@ziepe.ca, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tpm: use kfree_sensitive() for context and session buffers
Date: Thu, 16 Jul 2026 08:26:20 -0400 [thread overview]
Message-ID: <43b1aaf7cf0c036543aa371ccc5e77db26a386ff.camel@HansenPartnership.com> (raw)
In-Reply-To: <20260716000355.13825-1-skunkolee@gmail.com>
On Wed, 2026-07-15 at 18:03 -0600, Ivy Lopez wrote:
> The context_buf and session_buf fields in struct tpm_space contain
> TPM context blobs which may include sensitive cryptographic material.
That's not true ... at least not in a way that could be exfiltrated.
All cryptographically sensitive areas of the context are already
encrypted by the TPM with an internal key so they contain nothing
useful to an attacker.
Regards,
James
next prev parent reply other threads:[~2026-07-16 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 0:03 Ivy Lopez
2026-07-16 12:26 ` James Bottomley [this message]
2026-07-18 18:39 ` Jarkko Sakkinen
2026-07-18 20:19 ` Jarkko Sakkinen
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=43b1aaf7cf0c036543aa371ccc5e77db26a386ff.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=skunkolee@gmail.com \
/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
all inboxes | Powered by JetHome®