From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754175AbbESSKU (ORCPT ); Tue, 19 May 2015 14:10:20 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39695 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751523AbbESSKR (ORCPT ); Tue, 19 May 2015 14:10:17 -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: <20150519175510.GB26822@thunk.org> References: <20150519175510.GB26822@thunk.org> <20150519155532.GB2871@thunk.org> <31154.1431965087@warthog.procyon.org.uk> <555A88FB.7000809@kernel.org> <29742.1432025631@warthog.procyon.org.uk> <1752.1432049417@warthog.procyon.org.uk> <3253.1432052599@warthog.procyon.org.uk> To: "Theodore Ts'o" Cc: dhowells@redhat.com, Andy Lutomirski , Andy Lutomirski , Linus Torvalds , Michal Marek , David Woodhouse , 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: <4895.1432059008.1@warthog.procyon.org.uk> Date: Tue, 19 May 2015 19:10:08 +0100 Message-ID: <4896.1432059008@warthog.procyon.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Theodore Ts'o wrote: > Oh, so you are generating a one-time key for each kernel build, Yes. > and then dropping the public key into a cert which is then signed by some > trusted CA system? No. We compile the public key into the vmlinux binary and leave it at that. Trying to automatically sign the key would expose the signing key through the buildfarm. David