From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 0190E409 for ; Tue, 28 Jul 2015 17:04:19 +0000 (UTC) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2687B11B for ; Tue, 28 Jul 2015 17:04:18 +0000 (UTC) Received: by lafd3 with SMTP id d3so62247645laf.1 for ; Tue, 28 Jul 2015 10:04:16 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <30361.1438101879@warthog.procyon.org.uk> References: <20436.1438090619@warthog.procyon.org.uk> <1438096213.5441.147.camel@HansenPartnership.com> <1438097471.5441.152.camel@HansenPartnership.com> <1438099839.5441.165.camel@HansenPartnership.com> <1438100102.26913.183.camel@infradead.org> <30361.1438101879@warthog.procyon.org.uk> From: Andy Lutomirski Date: Tue, 28 Jul 2015 10:03:57 -0700 Message-ID: To: David Howells Content-Type: text/plain; charset=UTF-8 Cc: James Bottomley , Luis Rodriguez , "ksummit-discuss@lists.linuxfoundation.org" , Kyle McMartin Subject: Re: [Ksummit-discuss] [TECH TOPIC] Firmware signing List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Jul 28, 2015 at 9:44 AM, David Howells wrote: > Andy Lutomirski wrote: > >> I'd really like to replace "the system trusted keyring" with >> purpose-specific lists of keys. There are keys we trust to sign >> modules, there are keys we trust to sign kexec things, there will be >> keys to trust to sign firmware for any device, etc. > > I have some patches to restrict what a key is permitted to do - see the top > few patches here: > > http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=fwsign-pkcs7 > > This involves marking the X.509 certs with the intended use case (or relying > on the existing CA stuff for key-signing keys). This will require that we take any firmware vendor's key and rewrap it somehow into a new X.509 blob with a key usage constraint. Can't we just track this stuff in the kernel without adding yet another dependency on X.509? --Andy