linux-kernel - Re: [PATCH 0/8] MODSIGN: Use PKCS#7 for module signatures [ver #4]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1432297697.2450.53.camel@linux.vnet.ibm.com>
Date:	Fri, 22 May 2015 08:28:17 -0400
From:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
To:	David Howells <dhowells@...hat.com>
Cc:	"Luis R. Rodriguez" <mcgrof@...e.com>,
	Andy Lutomirski <luto@...capital.net>,
	Andy Lutomirski <luto@...nel.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Michal Marek <mmarek@...e.cz>,
	Matthew Garrett <mjg59@...f.ucam.org>, keyrings@...ux-nfs.org,
	Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Seth Forshee <seth.forshee@...onical.com>,
	LSM List <linux-security-module@...r.kernel.org>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH 0/8] MODSIGN: Use PKCS#7 for module signatures [ver #4]

On Fri, 2015-05-22 at 08:48 +0100, David Howells wrote:
> Luis R. Rodriguez <mcgrof@...e.com> wrote:
> 
> > > This is similar to what i am doing right now - create CA hierarchy so we can 
> > > have something like:
> > > 
> > >                                +-> KeyB
> > >                                |
> > > RootCA --->  CertA ---> CertB ---> CertC ---> KeyC
> > >                     |
> > >                     +-> CertA' ---> KeyA"
> > 
> > How exactly do you go about uploading CertB to the kernel BTW?
> 
> Assuming RootCA or CertA is present in the kernel, the idea would be to use
> the add_key() system call or the request_key() mechanism to add the key to the
> system keyring.  The key in the cert would only be added to the keyring if it
> is trusted by a key already there.

>From Petko's description, the RootCA is on the system keyring, but CertA
is on a new IMA trusted CA keyring.   So everything you said is true,
but on this new, yet to be upstreamed, IMA trusted CA keyring.

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/