From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752454AbdKHUJT (ORCPT ); Wed, 8 Nov 2017 15:09:19 -0500 Received: from mx2.suse.de ([195.135.220.15]:45665 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751716AbdKHUJS (ORCPT ); Wed, 8 Nov 2017 15:09:18 -0500 Date: Wed, 8 Nov 2017 21:09:16 +0100 From: "Luis R. Rodriguez" To: Mimi Zohar Cc: "Luis R. Rodriguez" , David Howells , linux-security-module@vger.kernel.org, gnomes@lxorguk.ukuu.org.uk, linux-efi , gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, Matthew Garrett , Marcus Meissner , "AKASHI, Takahiro" Subject: Re: Firmware signing -- Re: [PATCH 00/27] security, efi: Add kernel lockdown Message-ID: <20171108200916.GF22894@wotan.suse.de> References: <1509660086.3416.15.camel@linux.vnet.ibm.com> <150842463163.7923.11081723749106843698.stgit@warthog.procyon.org.uk> <14219.1509660259@warthog.procyon.org.uk> <1509660641.3416.24.camel@linux.vnet.ibm.com> <20171107230700.GJ22894@wotan.suse.de> <1510171269.4484.26.camel@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1510171269.4484.26.camel@linux.vnet.ibm.com> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 08, 2017 at 03:01:09PM -0500, Mimi Zohar wrote: > > > > Or reflect that IMA-appraisal, if enabled, will enforce firmware being > > > validly signed. > > > > But FWICT lockdown is a built-in kernel thingy, unless lockdown implies IMA > > it would not be the place to refer to it. > > > > It seems the documentation was proposed to help users if an error was caught. > > That error should cover only what is being addressed in code on the kernel. > > Enabling "lockdown" needs to take into account IMA-appraisal to > prevent breaking systems with it enabled. > > An IMA builtin "secure_boot" policy was already upstreamed (commit > 503ceaef8e2e "ima: define a set of appraisal rules requiring file > signatures").  An additional patch, automatically enables the > "secure_boot" policy in "lockdown" mode. > > Refer to this discussion and patch: > http://kernsec.org/pipermail/linux-security-module-archive/2017-October/003913.html > http://kernsec.org/pipermail/linux-security-module-archive/2017-October/003910.html Ah then yeah this makes sense to mesh into the lock down documentation. Luis