linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: tpm2@lists.linux.dev
Cc: linux-integrity@vger.kernel.org
Subject: tpm2-protocol: open for patches
Date: Tue, 26 Aug 2025 00:49:01 +0300	[thread overview]
Message-ID: <aKzaTYCI2GO_UPRB@kernel.org> (raw)

Hi

The last version that I do "as solo":

https://crates.io/crates/tpm2-protocol/0.10.10

I lifted up the version number in the main branch so that ABI breaks can
be done [1]. Consider all versions up 0.10.10 as the PoC era of this
project. I'm neither to motivated to pick up any stable fixes for 0.10.x.

Versions starting from 0.11 (once it is released) 0.11.x, bug fix
(no feature) branches can be done.

There's one feature in my test program (which I don't recommend to use
for any production, it's still heavily under construction) that I'm
willing to consider for relicensing and further to contribute e.g.,
to TPM-RS or perhaps as its own crate:

https://github.com/puavo-org/tpm2sh/blob/main/src/pretty_printer.rs

[lot's of unimplemented parts but it does not trip on them but instead
 marks them down to the log]

Keep in mind that the constraints in the following sections (taken from
lib.rs) are the existential limits for any possible patch (including
dev dependencies, do that type of stuff at your own personan sandbox
thank you).

## Constraints

* `alloc` is disallowed.
* Dependencies are disallowed.
* Developer dependencies (aka 'dev-dependencies`) are disallowed.
* Panics are disallowed.

## Design Goals

* The crate must compile with GNU make and rustc without any external
  dependencies.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/tpm2-protocol.git/commit/?id=d265c021c9407a93068c49a691a9534b1eff3099

BR, Jarkko

                 reply	other threads:[~2025-08-25 21:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=aKzaTYCI2GO_UPRB@kernel.org \
    --to=jarkko@kernel.org \
    --cc=linux-integrity@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).