From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757145Ab3BUSez (ORCPT ); Thu, 21 Feb 2013 13:34:55 -0500 Received: from mx1.redhat.com ([209.132.183.28]:10361 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756133Ab3BUSey (ORCPT ); Thu, 21 Feb 2013 13:34:54 -0500 Date: Thu, 21 Feb 2013 13:34:45 -0500 From: Peter Jones To: Linus Torvalds Cc: David Howells , Matthew Garrett , Josh Boyer , Vivek Goyal , Kees Cook , keyrings@linux-nfs.org, Linux Kernel Mailing List Subject: Re: [GIT PULL] Load keys from signed PE binaries Message-ID: <20130221183445.GB20629@fenchurch.internal.datastacks.com> References: <30665.1361461678@warthog.procyon.org.uk> <20130221164244.GA19625@srcf.ucam.org> <567.1361470653@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 21, 2013 at 10:25:47AM -0800, Linus Torvalds wrote: > - why do you bother with the MS keysigning of Linux kernel modules to > begin with? This is not actually what the patchset implements. All it's done here is using PE files as envelopes for keys. The usage this enables is to allow for whoever makes a module (binary only or merely out of tree for whatever reason) to sign it and vouch for it themselves. That could include, for example, a systemtap module. -- Peter