From: Casey Schaufler <casey@schaufler-ca.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
cinthya aranguren <cinthya.aranguren@gmail.com>
Cc: casey@schaufler-ca.com, selinux@tycho.nsa.gov,
LSM List <linux-security-module@vger.kernel.org>
Subject: Re: Removing DAC.
Date: Mon, 24 Mar 2008 11:13:54 -0700 (PDT) [thread overview]
Message-ID: <207587.93872.qm@web36605.mail.mud.yahoo.com> (raw)
In-Reply-To: <1206380713.3302.43.camel@moss-spartans.epoch.ncsc.mil>
--- Stephen Smalley <sds@tycho.nsa.gov> wrote:
>
> > This is a good point. I will experiment with CAP_DAC_OVERRIDE.
> > but .. why SELinux take DAC attributes into account when making
> > decisions ?? this does not violate the separation of "policy" from
> > "Enforcement" ??
>
> SELinux does not use the DAC attributes (uid, gid, mode bits) as part of
> its decision.
I stand corrected. Somehow I thought that uids came into the
equation, but I guess I was wrong.
> SELinux does however control the use of capabilities/privileges in
> accordance with its policy. And it does have a notion of user identity
> in its security context, although that is separately managed and is
> usually used just as a "role set" construct in modern SELinux (e.g.
> staff_u authorized for staff_r and sysadm_r).
That's were I was confusing things, the security context uid being
a component of the policy that is maintained in addition to the
traditional uid. Thank you for the clarification.
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:[~2008-03-24 18:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 15:54 Removing DAC cinthya aranguren
2008-03-23 17:25 ` Casey Schaufler
2008-03-23 17:40 ` Casey Schaufler
2008-03-24 17:29 ` cinthya aranguren
2008-03-24 17:45 ` Stephen Smalley
2008-03-24 18:13 ` Casey Schaufler [this message]
2008-03-24 17:20 ` cinthya aranguren
2008-03-24 18:01 ` Casey Schaufler
2008-03-23 22:34 ` Russell Coker
2008-03-24 12:12 ` Joshua Brindle
2008-03-24 12:48 ` Russell Coker
2008-03-24 17:53 ` cinthya aranguren
2008-03-24 12:20 ` Stephen Smalley
2008-03-25 4:41 ` Russell Coker
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=207587.93872.qm@web36605.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=cinthya.aranguren@gmail.com \
--cc=linux-security-module@vger.kernel.org \
--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.