From: Chris Wright <chrisw@sous-sol.org>
To: Michael Halcrow <mhalcrow@us.ibm.com>
Cc: Greg KH <greg@kroah.com>, Chris Wright <chrisw@sous-sol.org>,
Andrew Morton <akpm@osdl.org>,
serue@us.ibm.com, Stephen Smalley <sds@tycho.nsa.gov>,
Davi Arnaut <davi.arnaut@gmail.com>,
jmorris@namei.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] LSM: remove BSD secure level security module
Date: Wed, 2 Aug 2006 12:42:36 -0700 [thread overview]
Message-ID: <20060802194236.GV2654@sequoia.sous-sol.org> (raw)
In-Reply-To: <20060802191416.GA3227@us.ibm.com>
* Michael Halcrow (mhalcrow@us.ibm.com) wrote:
> On Wed, Aug 02, 2006 at 11:23:11AM -0700, Greg KH wrote:
> > On Wed, Aug 02, 2006 at 11:07:08AM -0700, Chris Wright wrote:
> > > This code has suffered from broken core design and lack of developer
> > > attention. Broken security modules are too dangerous to leave around.
> > > It is time to remove this one.
> > >
> > > Signed-off-by: Chris Wright <chrisw@sous-sol.org>
> > > Cc: Michael Halcrow <mhalcrow@us.ibm.com>
> > > Cc: Serge Hallyn <serue@us.ibm.com>
> > > Cc: Davi Arnaut <davi.arnaut@gmail.com>
> >
> > Don't know if it really matters, but I really agree. Feel free to add:
> > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> >
> > if you want to.
>
> Is this accomplished by dropping patches or by adding a patch to
> remove the files? In any case, here is a patch to do the latter...
I don't follow. I sent a patch...
thanks,
-chris
next prev parent reply other threads:[~2006-08-02 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 18:07 [PATCH] LSM: remove BSD secure level security module Chris Wright
2006-08-02 18:23 ` Greg KH
2006-08-02 19:14 ` Michael Halcrow
2006-08-02 19:42 ` Chris Wright [this message]
2006-08-02 18:59 ` James Morris
2006-08-02 19:11 ` Serge E. Hallyn
2006-08-02 19:33 ` Michael Halcrow
2006-08-02 19:44 ` Chris Wright
2006-08-02 22:10 ` Alan Cox
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=20060802194236.GV2654@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=akpm@osdl.org \
--cc=davi.arnaut@gmail.com \
--cc=greg@kroah.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=sds@tycho.nsa.gov \
--cc=serue@us.ibm.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