From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id EB2B2D54 for ; Fri, 7 Sep 2018 19:53:57 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 987F5A8 for ; Fri, 7 Sep 2018 19:53:57 +0000 (UTC) Date: Fri, 7 Sep 2018 16:53:50 -0300 From: Mauro Carvalho Chehab To: Justin Forbes Message-ID: <20180907165350.44039a6a@coco.lan> In-Reply-To: References: <17533.1536166384@warthog.procyon.org.uk> <32341.1536178494@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: James.Bottomley@hansenpartnership.com, Peter Jones , joeyli.kernel@gmail.com, ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [TECH TOPIC] Kernel lockdown and secure boot List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Em Wed, 5 Sep 2018 15:34:04 -0500 Justin Forbes escreveu: > On Wed, Sep 5, 2018 at 3:14 PM, David Howells wrote: > > Justin Forbes wrote: > > > >> Lockdown is a config option on it's own, just also add a separate > >> config option option to enable lockdown on UEFI secure boot. > > > > The patchset has that already (CONFIG_LOCK_DOWN_IN_EFI_SECURE_BOOT). > > > > One of the issues appears to be that we're making it boot-time conditional at > > all. If I understand him correctly, Linus seems to want us to make everything > > locked down at compile time or not at all. > > > > The last push attempt dropped that patch and did have the compile time > (CONFIG_LOCK_DOWN_MANDATORY) as well as an option for command line > enabling with lockdown=1 (CONFIG_LOCK_DOWN_KERNEL). It just didn't > have an option for triggering off of UEFI Secure Boot. As a distro, > running CONFIG_LOCK_DOWN_MANDATORY isn't much of an option. We ran > the 4.17 development series in rawhide with CONFIG_LOCK_DOWN_KERNEL, > and no one noticed that their secure boot was off. Heh, I actually had to turn secure boot off due to that :-) (long story short, it was on an Intel 8 gen CPU with Radeon GPU on it, with required 4.17 + DRM for 4.18 in order to detect my 3 monitors, so I had to build my own kernel, not signed by Red Hat). Thanks, Mauro