From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60924) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmm7P-0002Jg-9s for qemu-devel@nongnu.org; Wed, 21 Sep 2016 14:19:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bmm7J-0003K2-Ah for qemu-devel@nongnu.org; Wed, 21 Sep 2016 14:19:38 -0400 Received: from mail-co1nam03on0054.outbound.protection.outlook.com ([104.47.40.54]:32256 helo=NAM03-CO1-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmm7I-0003Jv-Uh for qemu-devel@nongnu.org; Wed, 21 Sep 2016 14:19:33 -0400 References: <147377800565.11859.4411044563640180545.stgit@brijesh-build-machine> <147377820679.11859.11888810000954712438.stgit@brijesh-build-machine> <20160914052834-mutt-send-email-mst@kernel.org> <20160914120943.GB24695@thinpad.lan.raisama.net> <20160921210055-mutt-send-email-mst@kernel.org> From: Brijesh Singh Message-ID: <44284e2f-dbba-c2e2-281f-c1def6c9f242@amd.com> Date: Wed, 21 Sep 2016 13:19:25 -0500 MIME-Version: 1.0 In-Reply-To: <20160921210055-mutt-send-email-mst@kernel.org> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH v1 20/22] fw_cfg: sev: disable dma in real mode List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" , Eduardo Habkost Cc: brijesh.singh@amd.com, Paolo Bonzini , crosthwaite.peter@gmail.com, armbru@redhat.com, p.fedin@samsung.com, qemu-devel@nongnu.org, lcapitulino@redhat.com, rth@twiddle.net Hi Michael, > > Again it isn't clear how much value does attestation have, > we are assuming arbitrary restrictions on the attacker such > as inability to trigger exits at random times, why not > assume it can't attack guest during boot? > IOW it seems reasonable to just ignore the need for attestation > completely as the first step. > Get the other stuff merged first. > Thanks for feedbacks. In v2, I will try to remove the attestation code and we can revisit it later. -Brijesh