From: Daniel J Walsh <dwalsh@redhat.com>
To: Darrel Goeddel <dgoeddel@TrustedCS.com>
Cc: Daniel J Walsh <Dan-Walsh@comcast.net>,
Stephen Smalley <sds@epoch.ncsc.mil>,
SELinux <SELinux@tycho.nsa.gov>
Subject: Re: Category Translation patch for MCS/MLS Policy
Date: Wed, 10 Aug 2005 07:30:02 -0400 [thread overview]
Message-ID: <42F9E53A.8080008@redhat.com> (raw)
In-Reply-To: <42F79E2C.7060006@trustedcs.com>
Darrel Goeddel wrote:
> Darrel Goeddel wrote:
>
>> Attached is our latest incarnation of the translation framework.
>
>
> Since I hit send before I actually attached the patch... The patch
> can be found at:
>
> http://home.insightbb.com/~dgoeddel/translation.patch
>
> Sorry about that.
>
Ok I will take a look at it.
One thing I also want to think about is a mechanism to prevent
translation for certain apps. One thing we are thinking about for MCS
is to allow an file to be in multiple categories. So a c1-c3
translation might look like
"MedicalRecords,MassGeneral,Cancer"
or
"CompanyConfidential,IBMNonDisclosure5"
So we would want files to show this, but if I do a ps -eZ command I
don't want "System High" processes to translate it.
So does MLS ps command translate? Or does MCS have to add the concept
of "system high"?
--
--
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-08-10 11:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 16:02 Category Translation patch for MCS/MLS Policy Daniel J Walsh
2005-08-08 17:43 ` Casey Schaufler
2005-08-08 19:33 ` Joshua Brindle
2005-08-08 17:56 ` Darrel Goeddel
2005-08-08 18:02 ` Darrel Goeddel
2005-08-10 11:30 ` Daniel J Walsh [this message]
2005-08-10 12:02 ` Stephen Smalley
2005-08-10 15:11 ` Casey Schaufler
2005-08-08 18:17 ` Colin Walters
-- strict thread matches above, loose matches on Subject: below --
2005-08-15 20:35 Chad Hanson
2005-08-16 12:56 ` 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=42F9E53A.8080008@redhat.com \
--to=dwalsh@redhat.com \
--cc=Dan-Walsh@comcast.net \
--cc=SELinux@tycho.nsa.gov \
--cc=dgoeddel@TrustedCS.com \
--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.