From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755772AbbESMwN (ORCPT ); Tue, 19 May 2015 08:52:13 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46475 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755173AbbESMwL (ORCPT ); Tue, 19 May 2015 08:52:11 -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: <1432039613.29806.75.camel@infradead.org> References: <1432039613.29806.75.camel@infradead.org> <555A88FB.7000809@kernel.org> <31154.1431965087@warthog.procyon.org.uk> <29742.1432025631@warthog.procyon.org.uk> To: David Woodhouse Cc: dhowells@redhat.com, Andy Lutomirski , Linus Torvalds , Michal Marek , Abelardo Ricart III , Linux Kernel Mailing List , Sedat Dilek , keyrings@linux-nfs.org, Rusty Russell , LSM List , Borislav Petkov , Jiri Kosina 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: <29121.1432039923.1@warthog.procyon.org.uk> Date: Tue, 19 May 2015 13:52:03 +0100 Message-ID: <29122.1432039923@warthog.procyon.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org David Woodhouse wrote: > Then when one module is loaded, we also have to pass in a table containing > all the other sha256's. The kernel checks the sha256 of what's being loaded, > checks it matches what's in the table that was also loaded. And then > validates the integrity of that table. That's basically Andy's idea with a special module containing the table. But unless you want to reload the table every time you load a module, you haven't gained anything. David