Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752088AbbESVrI (ORCPT ); Tue, 19 May 2015 17:47:08 -0400 Received: from cantor2.suse.de ([195.135.220.15]:47855 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751353AbbESVrG (ORCPT ); Tue, 19 May 2015 17:47:06 -0400 Date: Tue, 19 May 2015 23:47:02 +0200 (CEST) From: Jiri Kosina To: David Howells cc: "Theodore Ts'o" , 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 Subject: Re: Should we automatically generate a module signing key at all? In-Reply-To: <3253.1432052599@warthog.procyon.org.uk> Message-ID: References: <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> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 845 Lines: 20 On Tue, 19 May 2015, David Howells wrote: > That wouldn't very convenient for building our kernels in our build farm > - we have a lot of machines and all of them would have to be equiped > with the key. Besides, we *want* to discard the private key where > possible as soon as possible because then we can't leak it and we can't > be forced to disclose it. You can still have a dedicated machine that's used just for signing the binaries. That machine wouldn't be connected to the network, would be physically secured, and would sign through a serial line or so. -- Jiri Kosina SUSE Labs -- 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/