Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751985AbbESUlC (ORCPT ); Tue, 19 May 2015 16:41:02 -0400 Received: from mail-ig0-f174.google.com ([209.85.213.174]:34332 "EHLO mail-ig0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751409AbbESUlA (ORCPT ); Tue, 19 May 2015 16:41:00 -0400 MIME-Version: 1.0 In-Reply-To: <20150519200232.GM23057@wotan.suse.de> References: <20150519200232.GM23057@wotan.suse.de> From: "Luis R. Rodriguez" Date: Tue, 19 May 2015 13:40:38 -0700 X-Google-Sender-Auth: o5t2RbaPEHtXOHI2JNfRRCM86i8 Message-ID: Subject: Re: [RFD] linux-firmware key arrangement for firmware signing To: linux-security-module , James Morris , serge@hallyn.com Cc: "linux-kernel@vger.kernel.org" , linux-wireless , David Howells , Kyle McMartin , David Woodhouse , Seth Forshee , Greg Kroah-Hartman , Joey Lee , Rusty Russell , zohar@linux.vnet.ibm.com, Konstantin Ryabitsev Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 806 Lines: 16 On Tue, May 19, 2015 at 1:02 PM, Luis R. Rodriguez wrote: > Other than this last nitpick, any other concerns or recommendations ? Oh one more thing. I think we should decide on a digest algorithm we'd wish to be used for linux-firmware signing, distributions likely will want to just have this enabled =y in their kernel unless of course proper care is taken to also make sure such module is available early for initramfs uses. The digest algorithm can be different than what any distribution uses for their own module signing digest. Luis -- 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/