Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755981AbbEUOqR (ORCPT ); Thu, 21 May 2015 10:46:17 -0400 Received: from lan.nucleusys.com ([92.247.61.126]:43694 "EHLO zztop.nucleusys.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755791AbbEUOqL (ORCPT ); Thu, 21 May 2015 10:46:11 -0400 Date: Thu, 21 May 2015 17:45:52 +0300 From: Petko Manolov To: Greg Kroah-Hartman Cc: 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: <20150521144552.GD18164@localhost> Mail-Followup-To: Greg Kroah-Hartman , 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 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> <20150521061453.GC30864@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150521061453.GC30864@kroah.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Score: -1.0 (-) X-Spam-Report: Spam detection software, running on the system "zztop.nucleusys.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On 15-05-20 23:14:53, Greg Kroah-Hartman wrote: > > 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?) [...] Content analysis details: (-1.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1263 Lines: 29 On 15-05-20 23:14:53, Greg Kroah-Hartman wrote: > > 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?) I did not say the kernel should care about signatures. This is entirely user's choice. You care about authenticity, you require signature and verify it against "known good" certificate. s/you/distro/ I'm just saying that it would be nice to have this feature in case somebody need it. Luckily IMA has this functionality, although you'll have to work hard to get to use it. :) > What is verifying a firmware image signature in the kernel attesting that > isn't already known in userspace? The kernel is a lot better place to keep certificates and keys safe, compared to userland. Petko -- 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/