From: Casey Schaufler <casey@schaufler-ca.com>
To: 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:25:50 -0700 (PDT) [thread overview]
Message-ID: <613578.78683.qm@web36601.mail.mud.yahoo.com> (raw)
In-Reply-To: <50771f160803230854n18bd2a07q34eb154fc016f351@mail.gmail.com>
--- 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.
The LSM, which is the interface that SELinux uses to plug into
the rest of the kernel is explicity designed to allow additional
restrictions but not replacement or override of existing
restrictions. In the early days of LSM both restrictive models,
like what we have today, and authoritiative models, which would
allow replacement of traditional DAC where considered. The
authoritative model was rejected based on how easy it would be
for proprietary modules that had nothing to do with security to
exploit the interface.
I am currently putting some work into separating the LSM into
a pair of interface sets, one for the privilege model and one
for the additional restrictions. Once in place it could be
possible to create a privilege scheme that reports to the
traditional DAC that everyone has DAC override, and leave it
to SELinux (or whatever restrictive model you might prefer)
to make the only decision.
That work is not done, nor is there any assurance that it
might be accepted when it is. Since it would result in a
system where the privilege module and the access restriction
module could team up to provide an authoritative model
it is within reason that the arguments that blocked an
authoritative LSM could be raised again with the same result.
Now I'll ask the 37 cent question:
Why would you want to do that?
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:52 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 [this message]
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
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=613578.78683.qm@web36601.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.