Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267785AbUJNWOs (ORCPT ); Thu, 14 Oct 2004 18:14:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267769AbUJNWOA (ORCPT ); Thu, 14 Oct 2004 18:14:00 -0400 Received: from baythorne.infradead.org ([81.187.226.107]:46484 "EHLO baythorne.infradead.org") by vger.kernel.org with ESMTP id S267411AbUJNVxz (ORCPT ); Thu, 14 Oct 2004 17:53:55 -0400 Subject: Re: Fw: signed kernel modules? From: David Woodhouse To: Roman Zippel Cc: David Howells , "Rusty Russell (IBM)" , Greg KH , Arjan van de Ven , Joy Latten , lkml - Kernel Mailing List In-Reply-To: References: <1097626296.4013.34.camel@localhost.localdomain> <1096411448.3230.22.camel@localhost.localdomain> <1092403984.29463.11.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> <1097755890.318.700.camel@hades.cambridge.redhat.com> <1097764251.318.724.camel@hades.cambridge.redhat.com> <1097789060.5788.2001.camel@baythorne.infradead.org> Content-Type: text/plain Message-Id: <1097790753.5788.2031.camel@baythorne.infradead.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2.dwmw2.1) Date: Thu, 14 Oct 2004 22:52:33 +0100 Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by baythorne.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 807 Lines: 20 On Thu, 2004-10-14 at 23:36 +0200, Roman Zippel wrote: > No. I still don't know, why the kernel has to do this? You avoided to > answer this question already before. Partly to protect against accidentally-corrupted modules causing damage. Partly to allow a sysadmin (or more likely an IT department) to enforce a policy that only known and approved modules shall be loaded onto machines which they're expected to support. Partly to allow other support providers to do likewise, or at least to _detect_ the fact that unsupported modules are loaded. -- dwmw2 - 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/