From: James Bottomley <jejb@linux.ibm.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Stefan Berger" <stefanb@linux.ibm.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH] tpm: add backend for mssim
Date: Wed, 14 Dec 2022 07:43:24 -0500 [thread overview]
Message-ID: <c4d8937037a2f41b35e86498abfd23d2b0cd0030.camel@linux.ibm.com> (raw)
In-Reply-To: <Y5m48UP/E/RuvBHM@redhat.com>
On Wed, 2022-12-14 at 11:52 +0000, Daniel P. Berrangé wrote:
> It is a shame there isn't a standardized protocol for software TPM
> communication, as that'd avoid the need for multiple backends.
Technically the mssim protocol is the standard, being part of the
reference implementation, but practically it's terrible: Using two
ports per vTPM is hardly scalable in a cloud situation and, as you say,
it has no security. Ideally someone with TCG connections would try to
standardize a more scalable network server protocol, something nicely
rest based that identified the vTPM by say its EK name.
James
next prev parent reply other threads:[~2022-12-14 12:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 17:10 [PATCH] tpm: add backend for mssim James Bottomley
2022-12-12 13:43 ` Stefan Berger
2022-12-12 13:59 ` James Bottomley
2022-12-12 14:27 ` Stefan Berger
2022-12-12 14:32 ` James Bottomley
2022-12-12 14:44 ` Stefan Berger
2022-12-12 14:47 ` James Bottomley
2022-12-12 15:20 ` Stefan Berger
2022-12-12 15:28 ` James Bottomley
2022-12-12 15:46 ` Stefan Berger
2022-12-12 15:47 ` Daniel P. Berrangé
2022-12-12 16:38 ` James Bottomley
2022-12-12 16:59 ` Stefan Berger
2022-12-12 18:48 ` James Bottomley
2022-12-12 18:58 ` Stefan Berger
2022-12-12 19:12 ` James Bottomley
2022-12-12 19:32 ` Stefan Berger
2022-12-12 20:24 ` Stefan Berger
2022-12-12 21:36 ` James Bottomley
2022-12-12 22:02 ` Stefan Berger
2022-12-12 22:27 ` James Bottomley
2022-12-12 22:43 ` Stefan Berger
2022-12-14 11:52 ` Daniel P. Berrangé
2022-12-14 12:43 ` James Bottomley [this message]
2022-12-15 2:42 ` Stefan Berger
2022-12-14 11:55 ` Daniel P. Berrangé
2022-12-12 22:06 ` James Bottomley
2022-12-14 11:31 ` Daniel P. Berrangé
2022-12-14 12:47 ` James Bottomley
2022-12-14 14:17 ` Markus Armbruster
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=c4d8937037a2f41b35e86498abfd23d2b0cd0030.camel@linux.ibm.com \
--to=jejb@linux.ibm.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.ibm.com \
/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).