From: Casey Schaufler <casey@schaufler-ca.com>
To: Stephen Smalley <sds@tycho.nsa.gov>, selinux@tycho.nsa.gov
Cc: James Morris <jmorris@namei.org>,
Eric Paris <eparis@parisplace.org>,
"Serge E. Hallyn" <serue@us.ibm.com>,
"Christopher J. PeBenito" <cpebenito@tresys.com>,
Chad Sellers <csellers@tresys.com>
Subject: Re: [RFC v2][PATCH] selinux: enable authoritative granting of capabilities
Date: Fri, 15 Jun 2007 08:14:08 -0700 (PDT) [thread overview]
Message-ID: <955428.96537.qm@web36609.mail.mud.yahoo.com> (raw)
In-Reply-To: <1181917726.17547.750.camel@moss-spartans.epoch.ncsc.mil>
--- Stephen Smalley <sds@tycho.nsa.gov> wrote:
> Second RFC on this patch, collects up discussion and changes so far. If
> no objections, then this will be re-posted as just a [PATCH] on selinux
> and lkml.
>
> ---
>
> Extend SELinux to allow capabilities to be granted authoritatively
> based solely on SELinux policy, enabling users of SELinux to
> selectively reduce or fully eliminate the need for a "root" user and
> setuid executables. This provides an alternative approach to file
> capabilities without conflicting with it.
Why don't you just work with the people who are getting the
file capabilities working and integrate that into SELinux?
Why do you have to take this tangent and confuse everything?
There. An objection. I do not believe you've demonstrated that
using the proposed file capabilities can't get you what you
want, and that we don't need two implementations of the same
thing.
Casey Schaufler
casey@schaufler-ca.com
--
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:[~2007-06-15 15:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 14:28 [RFC v2][PATCH] selinux: enable authoritative granting of capabilities Stephen Smalley
2007-06-15 14:42 ` [RFC v2][PATCH] refpolicy: add memprotect and cap_override definitions and interfaces Stephen Smalley
2007-06-19 12:56 ` Christopher J. PeBenito
2007-06-15 15:14 ` Casey Schaufler [this message]
2007-06-15 15:27 ` [RFC v2][PATCH] selinux: enable authoritative granting of capabilities Stephen Smalley
2007-06-15 16:05 ` Casey Schaufler
2007-06-15 16:24 ` Karl MacMillan
2007-06-15 19:36 ` Stephen Smalley
2007-06-15 20:50 ` Casey Schaufler
2007-06-18 13:03 ` Stephen Smalley
2007-06-18 15:32 ` Casey Schaufler
2007-06-18 17:03 ` Stephen Smalley
2007-06-21 20:41 ` Casey Schaufler
2007-06-20 18:56 ` Stephen Smalley
2007-06-20 20:13 ` Serge E. Hallyn
2007-06-20 20:52 ` Stephen Smalley
2007-06-20 21:08 ` Serge E. Hallyn
2007-06-21 12:24 ` Stephen Smalley
2007-06-22 1:29 ` Linux user / SELinux user changes Hasan Rezaul-CHR010
2007-06-22 2:55 ` Ken YANG
2007-06-22 11:36 ` Stephen Smalley
2007-06-20 22:33 ` [RFC v2][PATCH] selinux: enable authoritative granting of capabilities Joshua Brindle
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=955428.96537.qm@web36609.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=cpebenito@tresys.com \
--cc=csellers@tresys.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@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 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.