From: Jarkko Sakkinen <jarkko@kernel.org>
To: tpm2@lists.linux.dev, linux-integrity@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: tpm2_protocol
Date: Wed, 13 Aug 2025 03:48:21 +0300 [thread overview]
Message-ID: <aJvg1UO_soccGwnY@kernel.org> (raw)
In-Reply-To: <aJve98-cGPKdEOlB@kernel.org>
On Wed, Aug 13, 2025 at 03:40:27AM +0300, Jarkko Sakkinen wrote:
> This is designed as unipolar TPM protocol stack i.e. it's designed not
> only send commands and receive responses, but also send responses and
> receive commands.
Unipolarity has been my design goal from the get go given that:
1. It enables high granularity filtering i.e. as capable or more capable
resource managers in kernel as pre-existing user space resource
managers (once the implementation has matured enough ofc but it
has the core design principles right I think).
2. Software defined TPM devices e.g., in-kernel TPM emulators and
interoperability layers for other crypto devices and confidential
computing technologies. I'm not sure if anyone wants anything
like this, just plain highilighting the possibilities.
BR, Jarkko
prev parent reply other threads:[~2025-08-13 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 12:59 tpm2_protocol Jarkko Sakkinen
2025-08-13 0:40 ` tpm2_protocol Jarkko Sakkinen
2025-08-13 0:48 ` Jarkko Sakkinen [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=aJvg1UO_soccGwnY@kernel.org \
--to=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tpm2@lists.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;
as well as URLs for NNTP newsgroup(s).