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 S1752777AbcDARId (ORCPT <rfc822;w@1wt.eu>);
	Fri, 1 Apr 2016 13:08:33 -0400
Received: from e23smtp07.au.ibm.com ([202.81.31.140]:33042 "EHLO
	e23smtp07.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751729AbcDARIb (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 1 Apr 2016 13:08:31 -0400
X-IBM-Helo: d23dlp02.au.ibm.com
X-IBM-MailFrom: zohar@linux.vnet.ibm.com
X-IBM-RcptTo: keyrings@vger.kernel.org;linux-kernel@vger.kernel.org;linux-security-module@vger.kernel.org
Message-ID: <1459530445.2657.74.camel@linux.vnet.ibm.com>
Subject: Re: [RFC PATCH 12/12] IMA: Use the the system trusted keyrings
 instead of .ima_mok [ver #3]
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
        linux-kernel@vger.kernel.org
Date: Fri, 01 Apr 2016 13:07:25 -0400
In-Reply-To: <28505.1459519603@warthog.procyon.org.uk>
References: <13142.1459437486@warthog.procyon.org.uk>
	 <1459426888.2657.26.camel@linux.vnet.ibm.com>
	 <1459166340.2751.52.camel@linux.vnet.ibm.com>
	 <20160309111814.28811.95697.stgit@warthog.procyon.org.uk>
	 <20160309111939.28811.7952.stgit@warthog.procyon.org.uk>
	 <12767.1459354776@warthog.procyon.org.uk>
	 <28505.1459519603@warthog.procyon.org.uk>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.12.11 (3.12.11-1.fc21) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 16040117-0025-0000-0000-000004285D30
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, 2016-04-01 at 15:06 +0100, David Howells wrote:
> David Howells <dhowells@redhat.com> wrote:
> 
> > The three choice options I implemented don't exactly provide new features.
> > Firstly:
> > 
> > 	config IMA_LOAD_X509
> > 
> > allow keys to be loaded in at compile time,
> 
> Ah - I think I'm labouring under a slight misapprehension here.  IMA_LOAD_X509
> doesn't load keys at compile time, but rather the kernel loads a file by name
> when booting, right?

Right, all certificates must be signed by a key on the builtin (or
secondary keyring) before being added to the IMA keyring.   Similarly,
dracut (modules/98integrity/ and systemd (ima-setup.c) have support for
loading signed certificates on the IMA keyring.

Mimi