From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932402AbWDUQOW (ORCPT ); Fri, 21 Apr 2006 12:14:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932400AbWDUQOV (ORCPT ); Fri, 21 Apr 2006 12:14:21 -0400 Received: from mail.kroah.org ([69.55.234.183]:30104 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S932402AbWDUQOT (ORCPT ); Fri, 21 Apr 2006 12:14:19 -0400 Date: Fri, 21 Apr 2006 08:05:29 -0700 From: Greg KH To: Jan Engelhardt Cc: Arjan van de Ven , James Morris , Christoph Hellwig , Andrew Morton , Stephen Smalley , T?r?k Edwin , linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, Chris Wright , Linus Torvalds Subject: Re: Time to remove LSM (was Re: [RESEND][RFC][PATCH 2/7] implementation of LSM hooks) Message-ID: <20060421150529.GA15811@kroah.com> References: <20060417162345.GA9609@infradead.org> <1145293404.8542.190.camel@moss-spartans.epoch.ncsc.mil> <20060417173319.GA11506@infradead.org> <20060417195146.GA8875@kroah.com> <1145462454.3085.62.camel@laptopd505.fenrus.org> <20060419201154.GB20545@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 21, 2006 at 03:30:26PM +0200, Jan Engelhardt wrote: > >> >> Well then, have a look at http://alphagate.hopto.org/multiadm/ > >> > > >> >hmm on first sight that seems to be basically an extension to the > >> >existing capability() code... rather than a 'real' LSM module. Am I > >> >missing something here? > >> > >> (So what's the definition for a "real" LSM module?) > > > >No idea, try submitting the patch :) > > > Because it's too big, you only get URLs: > > [01/02] http://alphagate.hopto.org/multiadm/mtadm_hooks-2.6.17-rc2.diff 137KB > [02/02] http://alphagate.hopto.org/multiadm/mtadm_module-2.6.17-rc2.diff 27KB > > Don't mention CodingStyle, I know. This is just a post to respond to the > topic on why noone submitted it earlier. > I already see it coming... I don't understand. Do you really want to get this module into the kernel? Or are you just posting it here for the link when people stumble across it in the archives? thanks, greg k-h