From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Ivan Gyurdiev <ivg2@cornell.edu>, SELinux@tycho.nsa.gov
Subject: Re: Multiple contexts
Date: Wed, 12 Jan 2005 18:18:14 +0000 [thread overview]
Message-ID: <20050112181814.GD26175@lkcl.net> (raw)
In-Reply-To: <1105542047.22495.69.camel@moss-spartans.epoch.ncsc.mil>
On Wed, Jan 12, 2005 at 10:00:47AM -0500, Stephen Smalley wrote:
> On Wed, 2005-01-12 at 09:44, Luke Kenneth Casson Leighton wrote:
> > ... how about encoding the file attributes in the policy files,
> > such that they are ACL-like?
>
> I don't follow your line of thinking.
sorry.
something simple:
i am thinking along the lines of more than one file context being
associated with a file - that sort of thing.
and permission being checked and allowed on either of the contexts.
in this way, someone can keep the default policy made for apache
(both the .te and the .fc file)
and can also create their own home-grown policy.
the issue of creating a special "samba_apache_file_type_t" and
deviating from two sets of standard policy files does seem...
somewhat archaic.
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:[~2005-01-12 18:07 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 20:50 Multiple contexts Ivan Gyurdiev
2005-01-10 23:23 ` Luke Kenneth Casson Leighton
2005-01-11 1:51 ` Luke Kenneth Casson Leighton
2005-01-11 20:09 ` Stephen Smalley
2005-01-11 21:48 ` Luke Kenneth Casson Leighton
2005-01-12 14:00 ` Stephen Smalley
2005-01-12 14:44 ` Luke Kenneth Casson Leighton
2005-01-12 15:00 ` Stephen Smalley
2005-01-12 18:18 ` Luke Kenneth Casson Leighton [this message]
2005-01-12 18:03 ` Stephen Smalley
2005-01-12 18:29 ` Luke Kenneth Casson Leighton
2005-01-12 21:27 ` Stephen Smalley
2005-01-12 22:41 ` Luke Kenneth Casson Leighton
2005-01-13 15:55 ` Stephen Smalley
2005-01-12 23:01 ` Luke Kenneth Casson Leighton
2005-01-13 16:03 ` Stephen Smalley
2005-01-13 16:44 ` Stephen Smalley
2005-01-13 17:17 ` Luke Kenneth Casson Leighton
2005-01-13 17:08 ` Stephen Smalley
2005-01-12 19:07 ` Luke Kenneth Casson Leighton
2005-01-11 15:18 ` Stephen Smalley
2005-01-11 20:08 ` Stephen Smalley
2005-01-12 20:11 ` Ivan Gyurdiev
2005-01-12 21:40 ` Stephen Bennett
2005-01-12 21:48 ` Stephen Smalley
2005-01-12 23:07 ` Luke Kenneth Casson Leighton
2005-01-13 16:06 ` Stephen Smalley
2005-01-12 21:47 ` Stephen Smalley
2005-01-12 23:08 ` Ivan Gyurdiev
2005-01-13 16:10 ` Stephen Smalley
2005-01-13 18:37 ` Luke Kenneth Casson Leighton
2005-01-13 23:17 ` Thomas Bleher
2005-01-14 7:07 ` Ivan Gyurdiev
2005-01-20 20:52 ` Ivan Gyurdiev
2005-01-12 23:32 ` Luke Kenneth Casson Leighton
2005-01-13 13:56 ` James Carter
2005-01-13 16:46 ` Luke Kenneth Casson Leighton
2005-01-13 16:16 ` Stephen Smalley
2005-01-13 16:48 ` Luke Kenneth Casson Leighton
2005-01-13 16:37 ` Stephen Smalley
2005-01-13 17:19 ` Luke Kenneth Casson Leighton
2005-01-13 17:10 ` Stephen Smalley
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=20050112181814.GD26175@lkcl.net \
--to=lkcl@lkcl.net \
--cc=SELinux@tycho.nsa.gov \
--cc=ivg2@cornell.edu \
--cc=sds@epoch.ncsc.mil \
/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.