From: Jarkko Sakkinen <jarkko@kernel.org>
To: linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Cc: linux-integrity@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: kselftest and cargo
Date: Tue, 16 Sep 2025 16:52:11 +0300 [thread overview]
Message-ID: <aMlri8uA2pf3_8M8@kernel.org> (raw)
In-Reply-To: <aMlqouOSU8XN7V5H@kernel.org>
On Tue, Sep 16, 2025 at 04:48:22PM +0300, Jarkko Sakkinen wrote:
> Hi,
>
> The pre-existing kselftest for TPM2 is derived works of my earlier Python
> based rudimentary TPM2 stack called 'tpm2-scripts'.
>
> In order to get more coverage and more mainintainable and extensible test
> suite I'd like to eventually rewrite the tests with bash and tpm2sh, which
> is a TPM2 cli written with Rust and based on my new TPM2 stack [1] [2].
>
> Given linux-rust work, would it be acceptable to require cargo to install
> a runner for kselftest? I'm finishing off now 0.11 version of the tool,
> which will take some time (versions before that are honestly quite bad,
> don't try them) but after that this would be something I'd like to
> put together.
>
> NOTE: while tpm2-protocol itself is Apache/MIT, tpm2sh is GPL3 licensed
> command-line program (for what it is worth).
Also tpm2-protocol is dependencyless, no crazy corporate TPM2
shenanigans and daemons involved etc., meaning that overall tpm2sh is
quite self-contained and good fit but 8 KSLOC not really to be imported
(the size comes from built-in TPM2 emulator, policy expression language
and advanced import functionality that directly converts PKCS#8 to TPM2
Key ASN.1 DEr/PEM all super useful for all sorts of testing purposes).
>
> [1] https://github.com/puavo-org/tpm2sh
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/tpm2-protocol.git/about/
>
> BR, Jarkko
>
>
next prev parent reply other threads:[~2025-09-16 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 13:48 kselftest and cargo Jarkko Sakkinen
2025-09-16 13:52 ` Jarkko Sakkinen [this message]
2025-09-16 22:39 ` Shuah Khan
2025-09-18 15:06 ` Jarkko Sakkinen
2025-09-18 15:15 ` Jarkko Sakkinen
2025-09-18 16:04 ` Shuah Khan
2025-09-18 16:35 ` 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=aMlri8uA2pf3_8M8@kernel.org \
--to=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).