linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:40:23 +0300	[thread overview]
Message-ID: <aJve98-cGPKdEOlB@kernel.org> (raw)
In-Reply-To: <aJs6rWexGNsH45_Z@kernel.org>

On Tue, Aug 12, 2025 at 03:59:25PM +0300, Jarkko Sakkinen wrote:
> I came up with this within 1,5 weeks not much sleep, and thought that
> this might be interesting to all of the three lists:

https://github.com/puavo-org/tpm2_library

Known issues; two tests are failing  They work when copy-pasted to cli
without any change, when run in a temporary subcommand, Not sure what 
is going on but looking into over time. And not all subcommands are
yet too well tested or polished ;-)

Features, reference and driver for this work is my earlier trial from
2014: https://github.com/ColinIanKing/tpm2-scripts

And partly this cover letter:
https://lore.kernel.org/linux-integrity/20240528210823.28798-1-jarkko@kernel.org/

[i was planning to update that patch set but was not happy with the
 tools so i decided to make my own.]

With those constraints I learned by trial and error to use macro_rules
and this the outcome. I'm looking forward to narrow the delta between
static estimate and run time 'len()' over time.

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.

BR, Jarkko


  reply	other threads:[~2025-08-13  0:40 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 ` Jarkko Sakkinen [this message]
2025-08-13  0:48   ` tpm2_protocol 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=aJve98-cGPKdEOlB@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).