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 10:10:25 -0700 [thread overview]
Message-ID: <20050826171024.GN7762@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1125057349.5812.35.camel@moss-spartans.epoch.ncsc.mil>
* Stephen Smalley (sds@tycho.nsa.gov) wrote:
> On Fri, 2005-08-26 at 07:48 -0400, Stephen Smalley wrote:
> > On Thu, 2005-08-25 at 15:51 -0700, Chris Wright wrote:
> > > @@ -3620,13 +3523,6 @@ static int selinux_netlink_send(struct s
> > > return err;
> > > }
> > >
> > > -static int selinux_netlink_recv(struct sk_buff *skb)
> > > -{
> > > - if (!cap_raised(NETLINK_CB(skb).eff_cap, CAP_NET_ADMIN))
> > > - return -EPERM;
> > > - return 0;
> > > -}
> > > -
> >
> > Hmm...is removing this entirely safe? Given that dummy is being
> > removed, and null ops are no longer being populated, don't we have to
> > ensure that we define a SELinux hook function for every cap_ function
> > and explicitly call that function? Likewise, don't we now have to add a
> > settime hook to SELinux to preserve behavior? Previously, it was
> > defaulting to the dummy hook, which conveniently called capable(), so it
> > ended up working regardless of whether SELinux was stacked with dummy or
> > capability.
>
> Ah, never mind - I forgot that you are falling back to the cap_
> functions in your static inlines if the operation is null. So you could
> also remove selinux_capset_set and selinux_task_post_setuid.
Thanks, I had done selinux_capset_set locally, but missed
selinux_task_post_setuid.
--
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 17:10 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 [this message]
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
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=20050826171024.GN7762@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.