From: Chris Wright <chrisw@osdl.org>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Chris Wright <chrisw@osdl.org>,
selinux@tycho.nsa.gov, linux-security-module@wirex.com
Subject: Re: [PATCH] remove selinux stacked ops
Date: Fri, 26 Aug 2005 09:22:41 -0700 [thread overview]
Message-ID: <20050826162241.GG7762@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1125059398.5812.53.camel@moss-spartans.epoch.ncsc.mil>
* Stephen Smalley (sds@tycho.nsa.gov) wrote:
> On Fri, 2005-08-26 at 07:58 -0400, Stephen Smalley wrote:
> > Ok, as with my prior comment, this one is also invalidated by the fact
> > that the static inlines fall back to the cap_ functions if the operation
> > is NULL. So I suppose this would work.
>
> Given these changes, what purpose does the capability module and the
> CONFIG_SECURITY_CAPABILITIES option serve anymore? Should capability.c
> be removed entirely?
I left it for two reasons. Making it built-in will mean you can't
load another security module. Some distros use the module already, so
it's compatibility. These aren't the best reasons to keep it long term.
> Also seems to obsolete the cap_stack module in the stacking patch set.
I believe so.
thanks,
-chris
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2005-08-26 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 22:17 selinux stacked ops Chris Wright
2005-08-25 22:51 ` [PATCH] remove " Chris Wright
2005-08-26 11:48 ` Stephen Smalley
2005-08-26 11:55 ` Stephen Smalley
2005-08-26 17:10 ` Chris Wright
2005-08-26 11:58 ` Stephen Smalley
2005-08-26 12:29 ` Stephen Smalley
[not found] ` <20050826163307.GA32690@immunix.com>
2005-08-26 12:54 ` serue
2005-08-26 16:55 ` Stephen Smalley
2005-08-26 16:22 ` Chris Wright [this message]
2005-08-26 16:50 ` Stephen Smalley
2005-08-26 17:06 ` Chris Wright
2005-08-26 11:08 ` Stephen Smalley
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=20050826162241.GG7762@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-security-module@wirex.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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.