From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Colin Walters <walters@redhat.com>, selinux@tycho.nsa.gov
Subject: Re: SELinux policy discussion.
Date: Fri, 17 Sep 2004 10:27:56 +0100 [thread overview]
Message-ID: <20040917092756.GA5296@lkcl.net> (raw)
In-Reply-To: <1095364389.10058.85.camel@localhost.localdomain>
On Thu, Sep 16, 2004 at 03:53:09PM -0400, Ivan Gyurdiev wrote:
> What I want from MAC is to restrict my applications while preserving
> 100% useful functionality and being transparent. I don't want more
> restrictions on my behavior. I don't want to be told that I can't use
then for _your_ requirements, i believe that the targetted policy
suits your needs must better than the strict one.
targetted policy restricts services but leaves users pretty much
unrestricted.
but remember that unix permissions are checked first _followed_ by
selinux permissions if the unix perms happen to succeed (so if the
unix perms fail there's no need to run the selinux security module).
l.
--
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:[~2004-09-17 9:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 20:03 SELinux policy discussion Daniel J Walsh
2004-09-16 0:38 ` Colin Walters
[not found] ` <1095302625.28466.56.camel@localhost.localdomain>
2004-09-16 4:05 ` Colin Walters
2004-09-16 4:15 ` Colin Walters
2004-09-16 12:25 ` Daniel J Walsh
2004-09-16 13:32 ` Stephen Smalley
[not found] ` <1095318426.32510.30.camel@localhost.localdomain>
2004-09-16 17:37 ` Colin Walters
2004-09-16 19:53 ` Ivan Gyurdiev
2004-09-17 9:27 ` Luke Kenneth Casson Leighton [this message]
2004-09-17 17:19 ` Valdis.Kletnieks
2004-09-18 23:50 ` Dax Kelson
2004-09-24 15:24 ` Russell Coker
2004-09-16 21:21 ` Daniel J Walsh
2004-09-16 21:46 ` Colin Walters
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=20040917092756.GA5296@lkcl.net \
--to=lkcl@lkcl.net \
--cc=ivg2@cornell.edu \
--cc=selinux@tycho.nsa.gov \
--cc=walters@redhat.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.