Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755913AbXFYOcf (ORCPT ); Mon, 25 Jun 2007 10:32:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754915AbXFYOc1 (ORCPT ); Mon, 25 Jun 2007 10:32:27 -0400 Received: from smtp112.sbc.mail.re2.yahoo.com ([68.142.229.93]:47403 "HELO smtp112.sbc.mail.re2.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1754903AbXFYOc0 (ORCPT ); Mon, 25 Jun 2007 10:32:26 -0400 X-YMail-OSG: V3XTwEkVM1kBIhorliMqXUZIaZ1wP_TKY2TTbjxOzFkDEPuocS2i6znmcst17Ai3.1KRaFttWg-- Date: Mon, 25 Jun 2007 09:32:22 -0500 From: "Serge E. Hallyn" To: Casey Schaufler Cc: "Serge E. Hallyn" , James Morris , linux-security-module@vger.kernel.org, Chris Wright , Andrew Morgan , Andrew Morton , Stephen Smalley , lkml , Arjan van de Ven , Greg KH , Eric Paris Subject: Re: [PATCH][RFC] security: Convert LSM into a static interface Message-ID: <20070625143222.GA11997@vino.hallyn.com> References: <20070625035743.GA8786@vino.hallyn.com> <350610.33706.qm@web36610.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <350610.33706.qm@web36610.mail.mud.yahoo.com> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1978 Lines: 53 Quoting Casey Schaufler (casey@schaufler-ca.com): > > --- "Serge E. Hallyn" wrote: > > > Quoting James Morris (jmorris@namei.org): > > > Convert LSM into a static interface, as the ability to unload a security > > > module is not required by in-tree users and potentially complicates the > > > overall security architecture. > > > > > > Needlessly exported LSM symbols have been unexported, to help reduce API > > > abuse. > > > > > > Module parameters for the capability and root_plug modules have been > > > converted to kernel parameters. > > > > > > The SECURITY_FRAMEWORK_VERSION macro has also been removed. > > > > Sigh, as much as I would *like* to stay out of this (I don't > > use modules at all on any system where I can avoid it), won't > > it make development - and especially testing - of new lsms > > much more painful and therefore less likely? > > While there's lots of pain involved in developing an LSM > modern development environments (e.g. virtual machines) > have reduced the value of loadable modules for debug purposes. > > > I realize there has been a dearth of new LSMs to date, > > but so much excitment over those proposed! > > > but if > > for instance a new solaris 10 based capability module were written, > > well, people would want to be able to > > > > rmmod capability > > modprobe cap_prm > > I think the value is overrated. You would never want to do that > in a production environment, and in a debug environment you could > just as easily reboot and get some start-up testing out of the way. And in a development environment you can just as easily select CONFIG_XYZ=y, no? So we have two options, one which provides greater choice and flexibility. -serge - 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/