From: Stefan Berger <stefanb@linux.ibm.com>
To: Jarkko Sakkinen <jarkko@kernel.org>, linux-integrity@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: boot-time vtpm helper (was "Re: <void>")
Date: Thu, 3 Aug 2023 08:46:52 -0400 [thread overview]
Message-ID: <4150bf8c-7321-0dab-ab54-dca7d54c1f3d@linux.ibm.com> (raw)
In-Reply-To: <CUISH28XXJGN.EWZ3CWAQ7G1C@suppilovahvero>
On 8/3/23 05:06, Jarkko Sakkinen wrote:
> On Thu Aug 3, 2023 at 11:25 AM EEST, Jarkko Sakkinen wrote:
>> Hi,
>>
>> I have a working PoC for boot-time initialization of vtpm inside
>> tpm_vtpm_proxy. ATM, it uses the Linux firmware interface to load a ELF
>> binary for the vtpm, and delivers a communication end for the helper
>> process.
>>
>> It is a great feature with the current narrow scope for continuous
>> integration. Obviously the scope could be later on extended to e.g.
Since VMs with vTPMs exist, which CI/CD environment would one use this in?
Where does the binary for the vtpm live when it's loaded with the firmware interface?
>> from unencrypted plain text to a vTPM living inside SGX enclave.
I would run swtpm inside an SGX enclave using Gramine.
Regards,
Stefan
>>
>> I could send an RFC of this, if there is wider interest for the
>> topic.
>>
>> BR, Jarkko
>
> I'm sorry, I'm trying learn aerc, and unfortunately forgot to add a subject.
>
> BR, Jarkko
next prev parent reply other threads:[~2023-08-03 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 8:25 Jarkko Sakkinen
2023-08-03 9:06 ` boot-time vtpm helper (was "Re: <void>") Jarkko Sakkinen
2023-08-03 12:46 ` Stefan Berger [this message]
2023-08-04 20:30 ` 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=4150bf8c-7321-0dab-ab54-dca7d54c1f3d@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®