From: Vivek Goyal Subject: Re: [RFC 1/1] ima: digital signature verification using asymmetric keys Date: Tue, 29 Jan 2013 11:58:53 -0500 Message-ID: <20130129165853.GC21930@redhat.com> References: <1358895228.2408.14.camel@falcor1> <20130125210157.GA13152@redhat.com> <20130128151527.GA5868@redhat.com> <20130128185625.GC5868@redhat.com> <1359404149.3906.75.camel@falcor1> <20130128202241.GB14405@redhat.com> <1359424135.3906.247.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: Content-Disposition: inline In-Reply-To: <1359424135.3906.247.camel@falcor1> Sender: linux-security-module-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Mon, Jan 28, 2013 at 08:48:55PM -0500, Mimi Zohar wrote: [..] > > Also given the fact that we allow loading policy from initramfs, root > > can rebuild initramfs and change the policy which takes effect over next > > reboot. So in priciple this works only when we are trying to impose some > > policy on non-root users? > > The assumption has always been that the initramfs would be measured, for > trusted boot, and appraised, for secure boot, before being executed. Hi Mimi, Ok. So for trusted boot, if initramfs is changed it will be detected. For secureboot, atleast right now initramfs is not signed and appraised. But I guess it could be added. But initramfs is generated by installer and installer does not have private keys to sign it. So distributions could not sign initramfs. Thanks Vivek