Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755048AbbEUGO5 (ORCPT ); Thu, 21 May 2015 02:14:57 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:45665 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753247AbbEUGOy (ORCPT ); Thu, 21 May 2015 02:14:54 -0400 Date: Wed, 20 May 2015 23:14:53 -0700 From: Greg Kroah-Hartman To: One Thousand Gnomes , Seth Forshee , "Luis R. Rodriguez" , linux-security-module@vger.kernel.org, james.l.morris@oracle.com, serge@hallyn.com, linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, David Howells , Kyle McMartin , David Woodhouse , Joey Lee , Rusty Russell , zohar@linux.vnet.ibm.com, mricon@kernel.org Subject: Re: [RFD] linux-firmware key arrangement for firmware signing Message-ID: <20150521061453.GC30864@kroah.com> References: <20150519200232.GM23057@wotan.suse.de> <20150520140426.GB126473@ubuntu-hedt> <20150520172446.4dab5399@lxorguk.ukuu.org.uk> <20150520164613.GD10473@localhost> <20150521044104.GH22632@kroah.com> <20150521054101.GA15037@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150521054101.GA15037@localhost> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1231 Lines: 27 On Thu, May 21, 2015 at 08:41:02AM +0300, Petko Manolov wrote: > > I too don't understand this need to sign something that you don't really know > > what it is from some other company, just to send it to a separate device that > > is going to do whatever it wants with it if it is signed or not. > > This is not the point. What you need to know is _where_ the firmware came from, > not _what_ it does once it reach your system. If you don't care about such > things, just ignore the signature. :) Ok, but how do we know "where"? Who is going to start signing and attesting to the validity of all of the firmware images in the linux-firmware tree suddenly? Why is it the kernel's job to attest this "where"? Shouldn't your distro/manufacturer be doing that as part of their "put this file on this disk" responsibilities (i.e. the package manager?) What is verifying a firmware image signature in the kernel attesting that isn't already known in userspace? thanks, greg k-h -- 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/