Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756813AbbEUP7p (ORCPT ); Thu, 21 May 2015 11:59:45 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33762 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756793AbbEUP7e (ORCPT ); Thu, 21 May 2015 11:59:34 -0400 Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: References: <31154.1431965087@warthog.procyon.org.uk> <555A88FB.7000809@kernel.org> <29742.1432025631@warthog.procyon.org.uk> <1752.1432049417@warthog.procyon.org.uk> <5261.1432060684@warthog.procyon.org.uk> <5566.1432061836@warthog.procyon.org.uk> To: Andy Lutomirski Cc: dhowells@redhat.com, "linux-kernel@vger.kernel.org" , keyrings@linux-nfs.org, LSM List Subject: Re: Should we automatically generate a module signing key at all? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9679.1432223969.1@warthog.procyon.org.uk> Date: Thu, 21 May 2015 16:59:29 +0100 Message-ID: <9680.1432223969@warthog.procyon.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 703 Lines: 16 Andy Lutomirski wrote: > Alternatively, we could eventually support some way of verifying a > hash or signature on each tuple (path, mode, contents) Since the initramfs is composed on the system being installed according to the hardware on that machine, you have to expose this list to meddling during composition whether you sign it (you need a private key) or hash it (what do you do with the hash once you've produced it?). David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/