public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, linux-security-module@wirex.com
Subject: Re: [PATCH] LSM changes for 2.5.50
Date: Thu, 5 Dec 2002 10:13:24 -0800	[thread overview]
Message-ID: <20021205181324.GA3867@kroah.com> (raw)
In-Reply-To: <20021205180646.A707@infradead.org>

On Thu, Dec 05, 2002 at 06:06:47PM +0000, Christoph Hellwig wrote:
> On Thu, Dec 05, 2002 at 10:03:58AM -0800, Greg KH wrote:
> > On Thu, Dec 05, 2002 at 05:00:02PM +0000, Christoph Hellwig wrote:
> > > On Thu, Dec 05, 2002 at 08:35:42AM -0800, Greg KH wrote:
> > > > ChangeSet 1.797.142.4, 2002/12/04 16:56:51-06:00, greg@kroah.com
> > > > 
> > > > LSM: add the example rootplug module
> > > 
> > > I don't think that's the kind of module that should be merged..
> > 
> > Why?  We have other "example" drivers in the kernel tree.  This is just
> > like that.
> 
> because it a) implements silly policy

That was the point :)
And I've seen sillier in "real" security products too...

> and b) violates layer rules.

What do you mean by this?  The fact that it abuses the USB core?  If so,
yes I agree with you, so I should probably move the "is this USB device
present" functionality into the USB core for everyone to use.  Would
that be better?

thanks,

greg k-h

  reply	other threads:[~2002-12-05 18:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05 16:31 [BK PATCH] LSM changes for 2.5.50 Greg KH
2002-12-05 16:32 ` [PATCH] " Greg KH
2002-12-05 16:33   ` Greg KH
2002-12-05 16:33     ` Greg KH
2002-12-05 16:34       ` Greg KH
2002-12-05 16:35         ` Greg KH
2002-12-05 17:00           ` Christoph Hellwig
2002-12-05 18:03             ` Greg KH
2002-12-05 18:06               ` Christoph Hellwig
2002-12-05 18:13                 ` Greg KH [this message]
2002-12-05 17:19   ` Christoph Hellwig
2002-12-05 18:03     ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021205181324.GA3867@kroah.com \
    --to=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox