[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140611022222.GA2349@srcf.ucam.org>
Date: Wed, 11 Jun 2014 03:22:22 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Mimi Zohar <zohar@...ux.vnet.ibm.com>
Cc: Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
Josh Boyer <jwboyer@...hat.com>,
David Howells <dhowells@...hat.com>,
Dmitry Kasatkin <d.kasatkin@...sung.com>,
keyrings <keyrings@...ux-nfs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-security-module <linux-security-module@...r.kernel.org>
Subject: Re: [PATCH 0/4] KEYS: validate key trust with owner and builtin keys
only
On Tue, Jun 10, 2014 at 09:24:53PM -0400, Mimi Zohar wrote:
> On Tue, 2014-06-10 at 22:40 +0100, Matthew Garrett wrote:
> > The hole is that the system trusts keys that you don't trust. The
> > appropriate thing to do is to remove that trust from the entire system,
> > not just one layer of the system. If people gain the impression that
> > they can simply pass a kernel parameter and avoid trusting the vendor
> > keys, they'll be upset to discover that it's easily circumvented.
>
> Assuming I remove all the keys I don't trust, there are still keys that
> are trusted while booting, but are not necessary afterwards. We should
> be able to limit the scope of where and when keys are trusted.
Providing a userspace mechanism for selectively dropping keys from the
kernel seems like a good thing?
--
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists