Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263540AbUJNMF2 (ORCPT ); Thu, 14 Oct 2004 08:05:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263743AbUJNMF2 (ORCPT ); Thu, 14 Oct 2004 08:05:28 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:17641 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S263540AbUJNMFW (ORCPT ); Thu, 14 Oct 2004 08:05:22 -0400 Date: Thu, 14 Oct 2004 14:01:46 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: David Howells cc: "Rusty Russell (IBM)" , David Woodhouse , Greg KH , Arjan van de Ven , Joy Latten , lkml - Kernel Mailing List Subject: Re: Fw: signed kernel modules? In-Reply-To: <16349.1097752349@redhat.com> Message-ID: References: <1097626296.4013.34.camel@localhost.localdomain> <1096411448.3230.22.camel@localhost.localdomain> <1092403984.29463.11.camel@bach> <1092369784.25194.225.camel@bach> <20040812092029.GA30255@devserv.devel.redhat.com> <20040811211719.GD21894@kroah.com> <1092097278.20335.51.camel@bach> <20040810002741.GA7764@kroah.com> <1092189167.22236.67.camel@bach> <19388.1092301990@redhat.com> <30797.1092308768@redhat.com> <20040812111853.GB25950@devserv.devel.redhat.com> <20040812200917.GD2952@kroah.com> <26280.1092388799@redhat.com> <27175.1095936746@redhat.com> <30591.1096451074@redhat.com> <10345.1097507482@redhat.com> <1097507755.318.332.camel@hades.cambridge.redhat.com> <1097534090.16153.7.camel@localhost.localdomain> <1097570159.5788.1089.camel@baythorne.infradead.org> <27277.1097702318@redhat.com> <16349.1097752349@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 767 Lines: 20 Hi, On Thu, 14 Oct 2004, David Howells wrote: > > How do you make sure that the module you sign is exactly the module that > > you want to get signed? > > Currently you have to sign them manually (as I said in that email). The Fedora > kernel spec file signs everything and its dog when you build the RPM. I'm trying to understand the reason to stuff this into kernel. Why can't this check be done before loading the module into the kernel? If you don't trust insmod, how can you trust the build system? bye, Roman - 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/