From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56617) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPJDd-0001FK-Rk for qemu-devel@nongnu.org; Mon, 18 Jul 2016 20:49:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bPJDc-0004Cj-0L for qemu-devel@nongnu.org; Mon, 18 Jul 2016 20:49:04 -0400 Received: from mail-yw0-x231.google.com ([2607:f8b0:4002:c05::231]:34578) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPJDa-0004Bt-Os for qemu-devel@nongnu.org; Mon, 18 Jul 2016 20:49:03 -0400 Received: by mail-yw0-x231.google.com with SMTP id i12so2988602ywa.1 for ; Mon, 18 Jul 2016 17:49:01 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1466716148-10655-1-git-send-email-mjg59@coreos.com> <20160715112923.GC2133@work-vm> Date: Mon, 18 Jul 2016 17:49:00 -0700 Message-ID: From: Matthew Garrett Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH] hw/misc: Add simple measurement hardware List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Berger Cc: stefanb@linux.vnet.ibm.com, qemu-devel@nongnu.org, "Daniel P. Berrange" , pbonzini@redhat.com, "Dr. David Alan Gilbert" On Jul 18, 2016 17:46, "Stefan Berger" wrote: > > > Matthew Garrett wrote on 07/18/2016 08:39:07 PM: > > > > > > On Jul 18, 2016 17:08, "Stefan Berger" wrote: > > > The point of the TPM is that the device that holds the state of > > the PCRs provides the signatures over their state rather than some > > other 'entity' whose trustworthiness wouldn't be clear. Admittedly > > the device comes with its own set of challenges. > > > The hypervisor holds the PCR state and also provides the signature. > > If the hypervisor is untrustworthy than the state of the virtualised > > system can never be verified, since it could simply have faked the > > measurements passed to whatever the root of trust is. > > So the hypervisor will have the key for signing and provide the quote ? Either the hypervisor itself or part of the associated platform. This framework is typically inside the same trust boundary.