From: Tyler Fanelli <tfanelli@redhat.com>
To: qemu-devel@nongnu.org
Cc: John Ferlan <jferlan@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: SEV guest attestation
Date: Wed, 24 Nov 2021 11:34:16 -0500 [thread overview]
Message-ID: <8b0c6f36-8a11-eeff-8bab-68c47fe95fbe@redhat.com> (raw)
Hi,
We recently discussed a way for remote SEV guest attestation through
QEMU. My initial approach was to get data needed for attestation through
different QMP commands (all of which are already available, so no
changes required there), deriving hashes and certificate data; and
collecting all of this into a new QMP struct (SevLaunchStart, which
would include the VM's policy, secret, and GPA) which would need to be
upstreamed into QEMU. Once this is provided, QEMU would then need to
have support for attestation before a VM is started. Upon speaking to
Dave about this proposal, he mentioned that this may not be the best
approach, as some situations would render the attestation unavailable,
such as the instance where a VM is running in a cloud, and a guest owner
would like to perform attestation via QMP (a likely scenario), yet a
cloud provider cannot simply let anyone pass arbitrary QMP commands, as
this could be an issue.
So I ask, does anyone involved in QEMU's SEV implementation have any
input on a quality way to perform guest attestation? If so, I'd be
interested. Thanks.
Tyler.
--
Tyler Fanelli (tfanelli)
next reply other threads:[~2021-11-24 16:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 16:34 Tyler Fanelli [this message]
2021-11-24 17:27 ` SEV guest attestation Tyler Fanelli
2021-11-24 17:49 ` Dr. David Alan Gilbert
2021-11-24 18:29 ` Tyler Fanelli
2021-11-24 17:57 ` Daniel P. Berrangé
2021-11-24 18:29 ` Dr. David Alan Gilbert
2021-11-25 7:14 ` Sergio Lopez
2021-11-25 12:44 ` Dov Murik
2021-11-25 13:42 ` Daniel P. Berrangé
2021-11-25 13:59 ` Dov Murik
2021-11-29 14:29 ` Brijesh Singh
2021-11-29 14:49 ` Brijesh Singh
2021-11-25 15:11 ` Sergio Lopez
2021-11-25 15:40 ` Dr. David Alan Gilbert
2021-11-25 15:56 ` Daniel P. Berrangé
2021-11-25 16:08 ` Dr. David Alan Gilbert
2021-11-29 13:33 ` Dov Murik
2021-11-25 13:20 ` Dr. David Alan Gilbert
2021-11-25 13:36 ` Daniel P. Berrangé
2021-11-25 13:52 ` Daniel P. Berrangé
2021-11-25 13:55 ` Dov Murik
2021-11-25 15:00 ` Dr. David Alan Gilbert
2021-11-25 13:27 ` Daniel P. Berrangé
2021-11-25 13:50 ` Dov Murik
2021-11-25 13:56 ` Daniel P. Berrangé
2021-11-25 15:19 ` Dr. David Alan Gilbert
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=8b0c6f36-8a11-eeff-8bab-68c47fe95fbe@redhat.com \
--to=tfanelli@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jferlan@redhat.com \
--cc=qemu-devel@nongnu.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).