From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Subject: Re: [PATCH 5/7] efi: Get the secure boot status [ver #3] Date: Fri, 25 Nov 2016 09:30:20 +0000 Message-ID: <15173.1480066220@warthog.procyon.org.uk> References: <1480016487.2444.18.camel@HansenPartnership.com> <147990561294.7576.6464430479448167484.stgit@warthog.procyon.org.uk> <147990565051.7576.9673287945782426886.stgit@warthog.procyon.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1480016487.2444.18.camel@HansenPartnership.com> Content-ID: <15172.1480066220.1@warthog.procyon.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: James Bottomley Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, dhowells@redhat.com, linux-security-module@vger.kernel.org, lukas@wunner.de, keyrings@vger.kernel.org, linux-arm-kernel@lists.infradead.org List-Id: linux-efi@vger.kernel.org James Bottomley wrote: > Since you seem to be using this to mean "is the platform locked down?", > this looks to be no longer complete in the UEFI 2.6 world. If > DeployedMode == 0, even if SecureBoot == 1 and SetupMode == 0, you can > remove the platform key by writing 1 to AuditMode and gain control of > the secure variables. The lock down state becomes DeployedMode == 1, > SecureBoot == 1 and SetupMode == 0 > > See the diagram on page 1817 > > http://www.uefi.org/sites/default/files/resources/UEFI%20Spec%202_6.pdf How many pages?! Does the DeployedMode variable not exist in older versions of the UEFI spec? David From mboxrd@z Thu Jan 1 00:00:00 1970 From: dhowells@redhat.com (David Howells) Date: Fri, 25 Nov 2016 09:30:20 +0000 Subject: [PATCH 5/7] efi: Get the secure boot status [ver #3] In-Reply-To: <1480016487.2444.18.camel@HansenPartnership.com> References: <1480016487.2444.18.camel@HansenPartnership.com> <147990561294.7576.6464430479448167484.stgit@warthog.procyon.org.uk> <147990565051.7576.9673287945782426886.stgit@warthog.procyon.org.uk> Message-ID: <15173.1480066220@warthog.procyon.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org James Bottomley wrote: > Since you seem to be using this to mean "is the platform locked down?", > this looks to be no longer complete in the UEFI 2.6 world. If > DeployedMode == 0, even if SecureBoot == 1 and SetupMode == 0, you can > remove the platform key by writing 1 to AuditMode and gain control of > the secure variables. The lock down state becomes DeployedMode == 1, > SecureBoot == 1 and SetupMode == 0 > > See the diagram on page 1817 > > http://www.uefi.org/sites/default/files/resources/UEFI%20Spec%202_6.pdf How many pages?! Does the DeployedMode variable not exist in older versions of the UEFI spec? David From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753429AbcKYJnm (ORCPT ); Fri, 25 Nov 2016 04:43:42 -0500 Received: from mx1.redhat.com ([209.132.183.28]:56858 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750997AbcKYJnc (ORCPT ); Fri, 25 Nov 2016 04:43:32 -0500 Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <1480016487.2444.18.camel@HansenPartnership.com> References: <1480016487.2444.18.camel@HansenPartnership.com> <147990561294.7576.6464430479448167484.stgit@warthog.procyon.org.uk> <147990565051.7576.9673287945782426886.stgit@warthog.procyon.org.uk> To: James Bottomley Cc: dhowells@redhat.com, lukas@wunner.de, linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, keyrings@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 5/7] efi: Get the secure boot status [ver #3] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <15172.1480066220.1@warthog.procyon.org.uk> Date: Fri, 25 Nov 2016 09:30:20 +0000 Message-ID: <15173.1480066220@warthog.procyon.org.uk> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Fri, 25 Nov 2016 09:30:24 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org James Bottomley wrote: > Since you seem to be using this to mean "is the platform locked down?", > this looks to be no longer complete in the UEFI 2.6 world. If > DeployedMode == 0, even if SecureBoot == 1 and SetupMode == 0, you can > remove the platform key by writing 1 to AuditMode and gain control of > the secure variables. The lock down state becomes DeployedMode == 1, > SecureBoot == 1 and SetupMode == 0 > > See the diagram on page 1817 > > http://www.uefi.org/sites/default/files/resources/UEFI%20Spec%202_6.pdf How many pages?! Does the DeployedMode variable not exist in older versions of the UEFI spec? David