On Wed, Feb 27, 2013 at 01:32:30PM +0100, Geert Uytterhoeven wrote:
> On Tue, Feb 26, 2013 at 11:06 PM, Peter Jones <pjo...@redhat.com> wrote:
> > On Tue, Feb 26, 2013 at 10:57:38PM +0100, Geert Uytterhoeven wrote:
> >
> >> BTW, I assume UEFI checks itself if enrolled hashes have been revoked,
> >> so it must phone home to some server? That must be disabled as well.
> >
> > No. Quit fearmongering.
>
> Good to know, thanks!
>
> So revocation will only be done by the guest OS?
> I.e. if I only boot my own trusted Linux, even if it's signed with the MS key,
> the MS key _on my system_ will never be revoked?
Something must apply the dbx update. We'll certainly do so in Fedora and
RHEL, from userland, but you're certainly in a position to make it not
happen in your own trusted linux, and even on a Fedora or RHEL machine
you maintain. But there's no "phoning home" involved - the plan is to
make that happen as a regular package update to shim-signed, so here you
go:
--- /etc/yum.conf.old 2013-02-27 09:10:25.181998268 -0500
+++ /etc/yum.conf 2013-02-27 09:10:34.423403583 -0500
@@ -21,3 +21,4 @@
# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d
+exclude=shim-signed
And as long as you never boot Windows on the thing, you're set.
--
Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
