From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1756881AbbEVM2c (ORCPT <rfc822;w@1wt.eu>);
	Fri, 22 May 2015 08:28:32 -0400
Received: from e28smtp08.in.ibm.com ([122.248.162.8]:44085 "EHLO
	e28smtp08.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1756821AbbEVM23 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 22 May 2015 08:28:29 -0400
Message-ID: <1432297697.2450.53.camel@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/8] MODSIGN: Use PKCS#7 for module signatures [ver #4]
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: "Luis R. Rodriguez" <mcgrof@suse.com>,
        Andy Lutomirski <luto@amacapital.net>,
        Andy Lutomirski <luto@kernel.org>,
        Rusty Russell <rusty@rustcorp.com.au>, Michal Marek <mmarek@suse.cz>,
        Matthew Garrett <mjg59@srcf.ucam.org>, keyrings@linux-nfs.org,
        Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Seth Forshee <seth.forshee@canonical.com>,
        LSM List <linux-security-module@vger.kernel.org>,
        David Woodhouse <dwmw2@infradead.org>
Date: Fri, 22 May 2015 08:28:17 -0400
In-Reply-To: <32540.1432280936@warthog.procyon.org.uk>
References: <20150521213829.GH23057@wotan.suse.de>
	 <20150515123513.16723.96340.stgit@warthog.procyon.org.uk>
	 <555BD715.40202@kernel.org> <31772.1432128969@warthog.procyon.org.uk>
	 <CALCETrUt+OO8sk=7j+rBToHujV7ONDzQ1Z6UMJ9HHUB44Jmtpw@mail.gmail.com>
	 <20150520162059.GC10473@localhost>
	 <32540.1432280936@warthog.procyon.org.uk>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.12.10 (3.12.10-1.fc21) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 15052212-0029-0000-0000-00000610C6E4
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, 2015-05-22 at 08:48 +0100, David Howells wrote:
> Luis R. Rodriguez <mcgrof@suse.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