From: Christoph Hellwig <hch@infradead.org>
To: Greg KH <greg@kroah.com>
Cc: "David S. Miller" <davem@redhat.com>,
becker@scyld.com, jmorris@intercode.com.au, kuznet@ms2.inr.ac.ru,
netdev@oss.sgi.com, linux-security-module@wirex.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] change format of LSM hooks
Date: Thu, 17 Oct 2002 14:21:49 +0100 [thread overview]
Message-ID: <20021017142149.A23181@infradead.org> (raw)
In-Reply-To: <20021016000706.GI16966@kroah.com>; from greg@kroah.com on Tue, Oct 15, 2002 at 05:07:06PM -0700
On Tue, Oct 15, 2002 at 05:07:06PM -0700, Greg KH wrote:
> On Tue, Oct 15, 2002 at 01:28:28PM -0700, Greg KH wrote:
> > On Tue, Oct 15, 2002 at 01:10:37PM -0700, David S. Miller wrote:
> > >
> > > I will not even look at the networking LSM bits until
> > > CONFIG_SECURITY=n is available.
BTW, there's another big issues with LSM: so far all those hook
have no user in a mergeable shape. For all other additions
there is a strong need to present something mergable but LSM
doesn't. IMHO we should require a pointer to a module in mergaable
shape (i.e. certainly not selinux) for each new hook addition.
next prev parent reply other threads:[~2002-10-17 13:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021015194545.GC15864@kroah.com>
[not found] ` <20021015.124502.130514745.davem@redhat.com>
[not found] ` <20021015201209.GE15864@kroah.com>
[not found] ` <20021015.131037.96602290.davem@redhat.com>
[not found] ` <20021015202828.GG15864@kroah.com>
2002-10-16 0:07 ` [RFC] change format of LSM hooks Greg KH
2002-10-16 0:03 ` David S. Miller
2002-10-16 8:15 ` Greg KH
2002-10-16 18:59 ` Greg KH
2002-10-16 16:33 ` joe perches
2002-10-16 23:46 ` Greg KH
2002-10-16 23:56 ` David S. Miller
2002-10-16 19:07 ` Greg KH
2002-10-17 1:41 ` Rusty Russell
2002-10-17 3:33 ` Daniel Phillips
2002-10-17 13:21 ` Christoph Hellwig [this message]
2002-10-17 16:55 ` Greg KH
2002-10-17 7:41 Rusty Russell
2002-10-17 17:20 ` [RFC] change format of LSM hooks Daniel Phillips
2002-10-18 2:04 ` Rusty Russell
2002-10-17 17:25 ` Daniel Phillips
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=20021017142149.A23181@infradead.org \
--to=hch@infradead.org \
--cc=becker@scyld.com \
--cc=davem@redhat.com \
--cc=greg@kroah.com \
--cc=jmorris@intercode.com.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.