From: Daniel J Walsh <dwalsh@redhat.com>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: MCS/Targeted Policy...
Date: Wed, 13 Jul 2005 10:41:59 -0400 [thread overview]
Message-ID: <42D52837.9050206@redhat.com> (raw)
We at Red Hat are working on a new type of Policy called MCS. (Multiple
Category Security)
A quick overview from James Morris..
>It's essentially a scheme where we take MLS and:
> - Ignore sensitivity levels
> - Allow users discretionary control over categories
> - Remove BLP constraints
>
>This is intended as a user-oriented extension to SELinux where DAC and TE
>are able to be further restricted by user assigned categories of the
>user's choosing e.g. "Company Confidential" or "Salary Information"
>
>Part of the idea is to make more general use of the MLS infrastructure and
>to try and enhance community traction.
>
We will describe it more in the future.
We would like to role this out in FC5, along with some other changes.
The biggest problem with it is upgrade.
We are turning on the fourth field (MLS) field of the security context,
but files on disk don't have this field now.
So we want to avoid a complete relabel, on upgrade. We would like to
have the kernel default all files to an MLS
field of s0. Some discussion of this has happened offline. And we are
looking for a way to do this without adding
a new field/type to the policy and requiring we rev the policy version.
One suggestion is that the kernel use the
initial_sids_file, and the "sid file" record.
sid file system_u:object_r:file_t:s0
The kernel could use this to default any missing field to the value from
this record.
-
--
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 reply other threads:[~2005-07-13 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 14:41 Daniel J Walsh [this message]
2005-07-13 15:51 ` MCS/Targeted Policy Casey Schaufler
2005-07-13 16:15 ` Daniel J Walsh
2005-07-13 16:32 ` Stephen Smalley
2005-07-14 1:36 ` James Morris
2005-07-14 3:34 ` Casey Schaufler
2005-07-14 16:17 ` James Morris
2005-07-15 4:37 ` Casey Schaufler
2005-07-18 13:23 ` James Morris
2005-07-19 0:00 ` Casey Schaufler
2005-07-19 13:51 ` Daniel J Walsh
2005-07-19 15:25 ` Casey Schaufler
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=42D52837.9050206@redhat.com \
--to=dwalsh@redhat.com \
--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.