[PATCH 0/9] KEYS: Blacklisting & UEFI database load
James.Bottomley at HansenPartnership.com
Wed Mar 7 15:28:37 UTC 2018
On Wed, 2018-03-07 at 08:18 -0500, Mimi Zohar wrote:
> On Tue, 2018-03-06 at 15:05 +0100, Jiri Slaby wrote:
> > what's the status of this please? Distributors (I checked SUSE,
> > RedHat and Ubuntu) have to carry these patches and every of them
> > have to forward-port the patches to new kernels. So are you going
> > to resend the PR to have this merged?
> Just because I trust the platform keys prior to booting the kernel,
> doesn't mean that I *want* to trust those keys once booted. There
> are, however, places where we need access to those keys to verify a
> signature (eg. kexec kernel image).
Which is essentially the reason I always give when these patches come
> Nayna Jain's "certs: define a trusted platform keyring" patch set
> introduces a new, separate keyring for these platform keys.
Perhaps, to break the deadlock, we should ask Jiří what the reason is
the distros want these keys to be trusted. Apart from the Microsoft
key, it will also give you an OEM key in your trusted keyring. Is it
something to do with OEM supplied modules?
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