From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Chad Hanson <chanson@TrustedCS.com>,
joe@nall.com, Darrel Goeddel <dgoeddel@TrustedCS.com>,
SELinux List <SELinux@tycho.nsa.gov>,
Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: Context translation and MLS categories
Date: Tue, 28 Feb 2006 12:08:07 -0500 [thread overview]
Message-ID: <44048377.2010707@cornell.edu> (raw)
In-Reply-To: <1141144322.22297.267.camel@moss-spartans.epoch.ncsc.mil>
>> What do I present to the user if they want their file accessible by
>> s0:c0, and s0:c3, but not the other two.
>>
>
> It doesn't work that way - it isn't an ACL. s0:c0,c3 means that the
> file can only be accessed by processes with both c0 and c3 in its
> low/sensitivity level (or high/clearance level in the MCS case). Adding
> a category to a file further restricts who can access it - it isn't
> additive.
>
Okay... so I am completely misunderstanding this.
That's good to know, before I make critical design mistakes.
I blame James Morris' howto :)
It has no examples with more than one category marked on a file.
============
Okay, how about....
1) We translate the entire range when displaying
2) When modifying the range, we unroll the user's range as (s,c) pairs,
then translate each of them, and present them as required clearances to
be added or removed
3) When the range is displayed again, re-translate the whole thing.
============
--
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:[~2006-02-28 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 5:37 Context translation and MLS categories Ivan Gyurdiev
2006-02-28 13:08 ` Stephen Smalley
2006-02-28 16:03 ` Ivan Gyurdiev
2006-02-28 16:32 ` Stephen Smalley
2006-02-28 17:08 ` Ivan Gyurdiev [this message]
2006-02-28 17:34 ` Stephen Smalley
2006-02-28 17:35 ` Ivan Gyurdiev
2006-02-28 18:11 ` 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=44048377.2010707@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux@tycho.nsa.gov \
--cc=chanson@TrustedCS.com \
--cc=dgoeddel@TrustedCS.com \
--cc=dwalsh@redhat.com \
--cc=joe@nall.com \
--cc=sds@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.