From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Subject: Re: [PATCH 6/7] efi: Handle secure boot from UEFI-2.6 [ver #7] Date: Wed, 01 Feb 2017 12:33:45 +0000 Message-ID: <20578.1485952425@warthog.procyon.org.uk> References: <148587558696.4026.16034622623568539004.stgit@warthog.procyon.org.uk> <148587564847.4026.5759345672956585977.stgit@warthog.procyon.org.uk> <10454.1485889162@warthog.procyon.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: Content-ID: <20577.1485952425.1@warthog.procyon.org.uk> Sender: owner-linux-security-module@vger.kernel.org To: Ard Biesheuvel Cc: dhowells@redhat.com, James Bottomley , Matt Fleming , "linux-efi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , linux-security-module , keyrings@vger.kernel.org, "linux-arm-kernel@lists.infradead.org" List-Id: linux-efi@vger.kernel.org Ard Biesheuvel wrote: > So this patch should take AuditMode into account, but not DeployedMode, i.e., > > SecureBoot == 0x1 > SetupMode == 0x0 > AuditMode == 0x0 (or non-existent) If we're in audit mode or setup mode SecureBoot==0 and SetupMode==1 according to the flowchart, so the check of AuditMode would seem redundant. Further, the checks above don't seem to differentiate deployed mode from user mode. Should they? David