From: Vivek Goyal Subject: Re: [RFC 1/1] ima: digital signature verification using asymmetric keys Date: Tue, 29 Jan 2013 11:30:36 -0500 Message-ID: <20130129163036.GB21930@redhat.com> References: <1358895228.2408.14.camel@falcor1> <20130125210157.GA13152@redhat.com> <20130128151527.GA5868@redhat.com> <20130128185242.GB5868@redhat.com> <1359402694.3906.53.camel@falcor1> <20130128201316.GA14405@redhat.com> <1359418442.3906.188.camel@falcor1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Kasatkin, Dmitry" , dhowells@redhat.com, jmorris@namei.org, linux-security-module@vger.kernel.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org To: Mimi Zohar Return-path: Received: from mx1.redhat.com ([209.132.183.28]:50267 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750809Ab3A2Qgk (ORCPT ); Tue, 29 Jan 2013 11:36:40 -0500 Content-Disposition: inline In-Reply-To: <1359418442.3906.188.camel@falcor1> Sender: linux-crypto-owner@vger.kernel.org List-ID: On Mon, Jan 28, 2013 at 07:14:02PM -0500, Mimi Zohar wrote: [..] > The 'trusted' keyring is a solution for installing only distro or third > party signed packages. How would a developer, for instance, create, > sign, and install his own package and add his public key safely? Hi Mimi, I guess using MOK, developer should be able to import his public key in shim database and in turn in kernel and use that to load user signed moduels. Thanks Vivek