From: Casey Schaufler <casey@schaufler-ca.com>
To: Stephen Smalley <sds@tycho.nsa.gov>, James Morris <jmorris@namei.org>
Cc: Chad Sellers <csellers@tresys.com>,
selinux@tycho.nsa.gov, Eric Paris <eparis@parisplace.org>,
"Serge E. Hallyn" <serue@us.ibm.com>
Subject: Re: [RFC][PATCH] selinux: enable authoritative granting of capabilities
Date: Thu, 14 Jun 2007 13:02:53 -0700 (PDT) [thread overview]
Message-ID: <374359.62085.qm@web36609.mail.mud.yahoo.com> (raw)
In-Reply-To: <1181843226.17547.669.camel@moss-spartans.epoch.ncsc.mil>
--- Stephen Smalley <sds@tycho.nsa.gov> wrote:
> Actually, the funny thing there is that selinux=0 would have the same
> effect if you had stripped the suid bits. Those applications would
> _only_ work with selinux enabled and enforcing.
Stephen's Evil Plan for World Domination revealed! I knew it!
I hope I'm kidding.
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-14 20:02 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 19:55 [RFC][PATCH] selinux: enable authoritative granting of capabilities Stephen Smalley
2007-06-11 20:39 ` James Morris
2007-06-11 20:43 ` Serge E. Hallyn
2007-06-11 21:43 ` Casey Schaufler
2007-06-11 22:20 ` James Morris
2007-06-12 0:00 ` Casey Schaufler
2007-06-12 11:46 ` Stephen Smalley
2007-06-11 22:24 ` Serge E. Hallyn
2007-06-12 9:20 ` Russell Coker
2007-06-12 15:44 ` Serge E. Hallyn
2007-06-12 15:57 ` Stephen Smalley
2007-06-13 11:16 ` Russell Coker
2007-06-13 12:31 ` Stephen Smalley
2007-06-14 9:44 ` Russell Coker
2007-06-14 11:03 ` Stephen Smalley
2007-06-14 14:50 ` Stephen Smalley
2007-06-14 14:54 ` Joshua Brindle
2007-06-14 13:54 ` Casey Schaufler
2007-06-14 14:50 ` Joshua Brindle
2007-06-14 15:05 ` Stephen Smalley
2007-06-12 11:43 ` Stephen Smalley
2007-06-12 11:31 ` Stephen Smalley
2007-06-12 9:27 ` Russell Coker
2007-06-12 12:09 ` Stephen Smalley
2007-06-12 12:50 ` Stephen Smalley
2007-06-12 15:08 ` Casey Schaufler
2007-06-12 15:33 ` Stephen Smalley
2007-06-12 16:38 ` Casey Schaufler
2007-06-12 17:49 ` James Morris
2007-06-12 19:56 ` Casey Schaufler
2007-06-12 16:03 ` Serge E. Hallyn
2007-06-12 13:24 ` Stephen Smalley
2007-06-12 20:50 ` Stephen Smalley
2007-06-12 21:12 ` Stephen Smalley
2007-06-13 14:31 ` Stephen Smalley
2007-06-13 15:06 ` Christopher J. PeBenito
2007-06-13 15:28 ` Stephen Smalley
2007-06-13 18:46 ` Christopher J. PeBenito
2007-06-13 19:20 ` Stephen Smalley
2007-06-14 19:19 ` Christopher J. PeBenito
2007-06-15 11:50 ` Stephen Smalley
2007-06-13 19:10 ` Eric Paris
2007-06-13 19:22 ` Stephen Smalley
2007-06-13 19:50 ` Daniel J Walsh
2007-06-13 20:00 ` Stephen Smalley
2007-06-13 20:22 ` Daniel J Walsh
2007-06-12 13:32 ` Stephen Smalley
2007-06-14 15:40 ` Chad Sellers
2007-06-14 15:55 ` Stephen Smalley
2007-06-14 16:03 ` Stephen Smalley
2007-06-14 16:13 ` Karl MacMillan
2007-06-14 16:52 ` James Morris
2007-06-14 17:28 ` Chad Sellers
2007-06-14 17:35 ` James Morris
2007-06-14 17:43 ` Chad Sellers
2007-06-14 17:47 ` Stephen Smalley
2007-06-14 20:02 ` Casey Schaufler [this message]
2007-06-14 17:46 ` Stephen Smalley
2007-06-14 18:18 ` James Morris
2007-06-14 15:55 ` Karl MacMillan
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=374359.62085.qm@web36609.mail.mud.yahoo.com \
--to=casey@schaufler-ca.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.