From: Casey Schaufler <casey@schaufler-ca.com>
To: casey@schaufler-ca.com,
cinthya aranguren <cinthya.aranguren@gmail.com>,
selinux@tycho.nsa.gov
Cc: LSM List <linux-security-module@vger.kernel.org>
Subject: Re: Removing DAC.
Date: Sun, 23 Mar 2008 10:40:57 -0700 (PDT) [thread overview]
Message-ID: <404587.40497.qm@web36614.mail.mud.yahoo.com> (raw)
In-Reply-To: <613578.78683.qm@web36601.mail.mud.yahoo.com>
--- Casey Schaufler <casey@schaufler-ca.com> wrote:
>
> --- cinthya aranguren <cinthya.aranguren@gmail.com> wrote:
>
> > Hi,
> >
> > Is there any way to avoid o remove DAC controls ? I'd like to have only one
> > security scheme in my system. I mean a pure SElinux system. not DAC + MAC.
> > only MAC.
>
> No.
>
> Well, not today.
I will add that if every process runs with CAP_DAC_OVERRIDE set
you can approach "no DAC", but I think you would probably have
to dig very deeply into the behavior of security cognizant
applications (sendmail comes to mind) and make sure that they
aren't explictly dropping that capability. I will let those
who work more closely with SELinux policy than I do describe
how capabilities possessed are related to an SELinux policy
and how that might impact the behavior of SELinux. You should
also note that SELinux takes what are traditionally DAC
attributes into account when making decisions and that if you
use MCS you are using a DAC mechanism within SELinux. I'm not
saying that's bad, just that it's there.
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-23 17:41 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 [this message]
2008-03-24 17:29 ` cinthya aranguren
2008-03-24 17:45 ` Stephen Smalley
2008-03-24 18:13 ` Casey Schaufler
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=404587.40497.qm@web36614.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=cinthya.aranguren@gmail.com \
--cc=linux-security-module@vger.kernel.org \
--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.