From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: David Windsor <dwindsor@gmail.com>, SELinux <selinux@tycho.nsa.gov>
Subject: Re: I would like to change the behavior of MCS label creations in directory.
Date: Tue, 27 Sep 2011 14:13:16 -0400 [thread overview]
Message-ID: <4E82123C.4070406@redhat.com> (raw)
In-Reply-To: <1317139611.22218.9.camel@moss-pluto>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/27/2011 12:06 PM, Stephen Smalley wrote:
> On Sat, 2011-09-24 at 18:05 -0400, David Windsor wrote:
>> On Fri, Sep 23, 2011 at 11:07 AM, Stephen Smalley
>> <sds@tycho.nsa.gov> wrote:
>>
>> <snip>
>>
>>>>
>>>> level_default file fromsource; == MLS; level_default file
>>>> fromtarget; == MCS;
>>>>
>>>> Anyone want to step forward and implement? :^)
>>>
>>> Need to distinguish low vs high. In MLS, you want to inherit
>>> the low level of the source/subject/process.
>>>
>>> Also, do you want the MCS behavior for all types or
>>> selectively? For example, if a svirt_t:s0:c256,c387 process
>>> creates a file in a :s0 directory (is that even possible?), do
>>> you really want that file to be :s0?
>>>
>>
>> Couldn't you use a range_transition in this case to specify an
>> exception to the default behavior for category inheritance?
>>
>> AFAICS, using rules such as
>> (user|role|type|level|range)_default, we're only specifying
>> default labeling behaviors for the different fields of a context.
>> More specific *_transition rules can exist in policy that should
>> override any defaults defined elsewhere.
>
> range_transition would only let you specify things like "When files
> are created by a process with domain D in a directory with type T,
> the range should be set to R.". Not rules of the form "Files
> created by processes in domain D1 should inherit their level from
> their creator while files created by processes in domain D2 should
> inherit their level from the parent directory."
>
I think this is a different more advanced language construct, that
frankly I don't care about right now. Implement it in CIL.
I have a problem I need to implement in F17/F18 time frame in order
for it to make RHEL7.
I only need to change the default for MCS to from
level_default file fromsource; == MLS;
to
level_default file fromtarget; == MCS;
I can not wait for the theoretical best fix that never comes.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6CEjwACgkQrlYvE4MpobNN/gCghV2LwrfGce50FdX7Iel0Z8pO
1IoAn3Vf7sXxz9qFsEnpoZQT6yIcjVUH
=sOyu
-----END PGP SIGNATURE-----
--
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:[~2011-09-27 18:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 19:53 I would like to change the behavior of MCS label creations in directory Daniel J Walsh
2011-09-22 20:13 ` Guido Trentalancia
2011-09-22 20:31 ` Stephen Smalley
2011-09-22 20:32 ` Daniel J Walsh
2011-09-22 20:37 ` Stephen Smalley
2011-09-22 20:42 ` Stephen Smalley
2011-09-23 15:01 ` Daniel J Walsh
2011-09-23 15:07 ` Stephen Smalley
2011-09-23 16:06 ` Guido Trentalancia
2011-09-23 17:33 ` Daniel J Walsh
2011-09-24 22:05 ` David Windsor
2011-09-27 16:06 ` Stephen Smalley
2011-09-27 16:50 ` David Windsor
2011-09-27 16:51 ` Stephen Smalley
2011-09-27 18:13 ` Daniel J Walsh [this message]
2011-10-14 15:57 ` Daniel J Walsh
2011-10-18 12:34 ` Christopher J. PeBenito
[not found] ` <00243337-937e-4e6b-880b-ba2f351112e7@email.android.com>
2011-10-18 22:07 ` David Windsor
2011-10-19 16:55 ` Stephen Smalley
2011-10-19 15:31 ` Joshua Brindle
2011-10-19 16:26 ` Stephen Smalley
2011-11-22 18:59 ` Eric Paris
2011-11-22 19:25 ` Stephen Smalley
2011-11-22 19:37 ` Eric Paris
2011-11-22 19:39 ` Stephen Smalley
2011-11-22 19:42 ` Eric Paris
2011-10-19 16:36 ` Kyle Moffett
2011-10-19 17:41 ` Daniel J Walsh
2011-10-19 17:47 ` Joshua Brindle
2011-10-19 17:50 ` Daniel J Walsh
2011-09-22 20:41 ` Guido Trentalancia
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=4E82123C.4070406@redhat.com \
--to=dwalsh@redhat.com \
--cc=dwindsor@gmail.com \
--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.