rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Daniel Almeida <daniel.almeida@collabora.com>
Cc: rust-for-linux@vger.kernel.org, linux-integrity@vger.kernel.org
Subject: Re: Using Rust on non-Rust side of kernel
Date: Sun, 24 Aug 2025 02:50:29 +0300	[thread overview]
Message-ID: <aKpTxSIBjLhW4eTL@kernel.org> (raw)
In-Reply-To: <aKpRjgkhz5C9YM-o@kernel.org>

On Sun, Aug 24, 2025 at 02:41:06AM +0300, Jarkko Sakkinen wrote:
> doing "hybrid solutions". I'm only starting to learn of the 
> possible integration options. I.e. not even debating of anything,
> only learning.

I.e. I don't know what I'm doing, thus asking random questions :-)

I do know however that my implementation is somewhat solid piece of code
and with high odds best available implementation of TPM2 protocol
marshalling and unmarshalling, at least as per core architecture (needs
obviously still maturization, I wrote it all in three weeks).

It's also complex enough problem (as people have done somewhat unsuccessful
attempts for past decaede) that we don't want to solve it twice (i.e.
for TPM-RS and kernel). It's fully isolated from the context.

I've also talked with some companies and people working on e.g. keystores,
and they've fully grabbed the idea how something like this can be used
as interop layer (i.e. a keystore acting TPM2), which further supports
an import model for this code (while it can be installed through cargo
too).

It coverages TCG version 184 specs and my idea is that with a new vger
list future spec updates could be managed in controlled fashion, and
we can build a process for imports.

BR, Jarkko

  reply	other threads:[~2025-08-23 23:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-23 12:12 Using Rust on non-Rust side of kernel Jarkko Sakkinen
2025-08-23 12:22 ` Jarkko Sakkinen
     [not found]   ` <BE42A51A-60C4-4E79-8459-CADEAB8DC3BA@collabora.com>
2025-08-23 23:06     ` Jarkko Sakkinen
2025-08-23 23:12       ` Jarkko Sakkinen
2025-08-24  1:12         ` Daniel Almeida
2025-08-24  7:15           ` Jarkko Sakkinen
2025-08-24  9:21             ` Jarkko Sakkinen
2025-08-23 23:41     ` Jarkko Sakkinen
2025-08-23 23:50       ` Jarkko Sakkinen [this message]
2025-08-25 12:04 ` Jonathan McDowell
2025-08-25 19:30   ` Jarkko Sakkinen
2025-08-25 19:42     ` Jarkko Sakkinen
2025-08-25 22:29       ` Jarkko Sakkinen
2025-08-25 23:23         ` Jarkko Sakkinen
2025-08-26  8:35     ` Jonathan McDowell
2025-08-26  8:56       ` Jarkko Sakkinen
2025-08-26  9:13         ` 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=aKpTxSIBjLhW4eTL@kernel.org \
    --to=jarkko@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=rust-for-linux@vger.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).