From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757137AbcCaPzs (ORCPT ); Thu, 31 Mar 2016 11:55:48 -0400 Received: from e28smtp01.in.ibm.com ([125.16.236.1]:39179 "EHLO e28smtp01.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751243AbcCaPzq (ORCPT ); Thu, 31 Mar 2016 11:55:46 -0400 X-IBM-Helo: d28relay02.in.ibm.com X-IBM-MailFrom: zohar@linux.vnet.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org;keyrings@vger.kernel.org;linux-security-module@vger.kernel.org Message-ID: <1459439733.2657.41.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 To: David Howells Cc: linux-security-module@vger.kernel.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org Date: Thu, 31 Mar 2016 11:55:33 -0400 In-Reply-To: <13142.1459437486@warthog.procyon.org.uk> References: <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> <13142.1459437486@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-cbid: 16033115-4790-0000-0000-00000E840DDD Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2016-03-31 at 16:18 +0100, David Howells wrote: > Mimi Zohar wrote: > > > You said you didn't want this option above (to quote: In this patch, the > > > choice should be between checking just the builtin trusted keys or both the > > > builtin trusted and secondary keys.) > > > > Does the ability of adding builtin X.509 certificates directly to the > > IMA keyring already exist or is it something that still needs to be > > done? Assuming the latter, this option would be added with the ability > > of adding X.509 certificates directly to the IMA keyring. > > I don't know what you mean by "directly" here. Even without this patch, you > can already add X.509 certs to the .ima keyring, both at compile time I'm must be missing something obvious here. I need to review the patches again. The builtin keys are loaded onto the .builtin_trusted_keys keyring, not the IMA keyring. Mimi > and at > runtime. This patch doesn't take that away - except by explicitly setting the > option to prevent runtime addition. > > David >