[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1441164905.17898.86.camel@linux.vnet.ibm.com>
Date: Tue, 01 Sep 2015 23:35:05 -0400
From: Mimi Zohar <zohar@...ux.vnet.ibm.com>
To: "Luis R. Rodriguez" <mcgrof@...e.com>
Cc: Kees Cook <keescook@...omium.org>,
David Woodhouse <dwmw2@...radead.org>,
David Howells <dhowells@...hat.com>,
Andy Lutomirski <luto@...capital.net>,
"Roberts, William C" <william.c.roberts@...el.com>,
"linux-security-module@...r.kernel.org"
<linux-security-module@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-wireless <linux-wireless@...r.kernel.org>,
"james.l.morris@...cle.com" <james.l.morris@...cle.com>,
"serge@...lyn.com" <serge@...lyn.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Paul Moore <paul@...l-moore.com>,
Eric Paris <eparis@...isplace.org>,
SE Linux <selinux@...ho.nsa.gov>,
Stephen Smalley <sds@...ho.nsa.gov>,
"Schaufler, Casey" <casey.schaufler@...el.com>,
"Luis R. Rodriguez" <mcgrof@...not-panic.com>,
Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Peter Jones <pjones@...hat.com>, Takashi Iwai <tiwai@...e.de>,
Ming Lei <ming.lei@...onical.com>, Joey Lee <jlee@...e.de>,
Vojtěch Pavlík <vojtech@...e.com>,
Kyle McMartin <kyle@...nel.org>,
Seth Forshee <seth.forshee@...onical.com>,
Matthew Garrett <mjg59@...f.ucam.org>,
Johannes Berg <johannes@...solutions.net>,
Jay Schulist <jschlst@...ba.org>,
Daniel Borkmann <dborkman@...hat.com>,
Alexei Starovoitov <ast@...mgrid.com>
Subject: Re: Linux Firmware Signing
On Wed, 2015-09-02 at 02:09 +0200, Luis R. Rodriguez wrote:
> On Tue, Sep 01, 2015 at 01:20:37PM -0700, Kees Cook wrote:
> > On Thu, Aug 27, 2015 at 2:29 PM, Luis R. Rodriguez <mcgrof@...e.com> wrote:
> > As long as the LSM know what kind of file it's loading, and has access
> > to the fd (and for IMA, the blob loaded from that fd), that should be
> > everything it needs. IMA has the name and blob, loadpin has the fd,
> > and a future signature-checking LSM could be able to look up signature
> > type from the load type, and split the key off (or fetch the key file)
> > itself.
I assume "and for IMA, the blob loaded from that fd" is referring to
the file signature stored in the xattr.
> OK great, I think that instead of passing the actual routine name we should
> instead pass an enum type for to the LSM, that'd be easier to parse and we'd
> then have each case well documented. Each LSM then could add its own
> documetnation for this and can switch on it. If we went with a name we'd have
> to to use something like __func__ and then parse that, its not clear if we need
> to get that specific.
Agreed. IMA already defines an enumeration.
/* IMA policy related functions */
enum ima_hooks { FILE_CHECK = 1, MMAP_CHECK, BPRM_CHECK, MODULE_CHECK,
FIRMWARE_CHECK, POLICY_CHECK, POST_SETATTR };
Mimi
--
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