[GIT PULL] Kernel lockdown for secure boot
gregkh at linuxfoundation.org
Wed Apr 4 13:57:38 UTC 2018
On Wed, Apr 04, 2018 at 09:34:11AM -0400, Theodore Y. Ts'o wrote:
> On Wed, Apr 04, 2018 at 03:02:33PM +0200, Greg Kroah-Hartman wrote:
> > On Wed, Apr 04, 2018 at 08:57:43AM -0400, Theodore Y. Ts'o wrote:
> > > On Wed, Apr 04, 2018 at 04:30:18AM +0000, Matthew Garrett wrote:
> > > > What I'm afraid of is this turning into a "security" feature that ends up
> > > > being circumvented in most scenarios where it's currently deployed - eg,
> > > > module signatures are mostly worthless in the non-lockdown case because you
> > > > can just grab the sig_enforce symbol address and then kexec a preamble that
> > > > flips it back to N regardless of the kernel config.
> > >
> > > Whoa. Why doesn't lockdown prevent kexec? Put another away, why
> > > isn't this a problem for people who are fearful that Linux could be
> > > used as part of a Windows boot virus in a Secure UEFI context?
> > Because no one is afraid of that :)
> Well, this is the excuse used by Windows.
Really? Every time I have tried to actually follow up on this
statement, it turns into an urban myth. If you have proof of this,
please let me know, otherwise I am going to keep saying it is false.
> Some more cynical people
> believe it's really an anti-competitvie thing, but we should
> acknowledge this is what is causing the fear that some distros have
> that their UEFI secure boot certs will be revoked by Microsoft if they
> don't have this crazy lockdown enforcement for UEFI Secure Boot.
Unsubstantiated fear of relying on another company's signing key to
suddenly stop working is worrying. But it's just that, fear, and not
anything that is actually true. We have a working shim binary that is
signed, in use by all distros and other operating systems (community and
corporate). To revoke that key now would be insane on a variety of
So let's stop playing the myth and fear card people, and focus on the
actual facts here.
> And I would all be for having the Kconfig description says, "This
> config option is only needed by distros who are fearful of Microsoft
> revoking their UEFI secure boot certificate."
Again, no fear please, facts only.
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the Linux-security-module-archive