From: Ivan Gyurdiev <ivg2@cornell.edu>
To: SELinux List <SELinux@tycho.nsa.gov>
Cc: Daniel J Walsh <dwalsh@redhat.com>
Subject: Context translation and MLS categories
Date: Tue, 28 Feb 2006 00:37:36 -0500 [thread overview]
Message-ID: <4403E1A0.8030704@cornell.edu> (raw)
To integrate selinux with nautilus, I'd like to have a function which
provides me with a list of translated (sensitivity, category) pairs, as
setrans.conf specifies. Then I can present a list of those strings to
the user.
The question is...where should this function be located, and what kind
of API will it have?
Currently I have a raw context that is supplied by gnome-vfs. Clearly I
need to break that down into fields. I want the user to configure the
individual fields, not have a box to type in the context. This breakdown
seems like it should be internal to selinux libraries. A good place to
do it is in the sepol context record. However, currently libsepol is
completely unaware of translations - all it can do is supply the raw mls
range, or possibly expand the mls range into some other format - like a
list of (sens, cat) pairs.
That still leaves translation to be done... but libselinux does not
provide any API for doing translation at the level of an mls range, or
even an individual (sensitivty, category) pair. It only allows
translation at the context level. Why is translation done at the context
level, and can I add additional APIs to translate at mls_range, or
individual sensitivity/category level. How does this affect the MITRE
translation library that I've been hearing about?
--
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:[~2006-02-28 5:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 5:37 Ivan Gyurdiev [this message]
2006-02-28 13:08 ` Context translation and MLS categories Stephen Smalley
2006-02-28 16:03 ` Ivan Gyurdiev
2006-02-28 16:32 ` Stephen Smalley
2006-02-28 17:08 ` Ivan Gyurdiev
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=4403E1A0.8030704@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux@tycho.nsa.gov \
--cc=dwalsh@redhat.com \
/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.