From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: Xavier Toth <txtoth@gmail.com>
Cc: Joe Nall <joe@nall.com>, SELinux List <selinux@tycho.nsa.gov>,
James Carter <jwcart2@tycho.nsa.gov>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [RFC] Add color translation support to mcstransd
Date: Fri, 05 Dec 2008 20:12:17 -0500 [thread overview]
Message-ID: <4939D171.5090705@tycho.nsa.gov> (raw)
In-Reply-To: <4939C7D8.7020000@tycho.nsa.gov>
Eamon Walsh wrote:
> I have placed the code into a git repository which can be checked out with:
> git-clone git://people.freedesktop.org/~ewalsh/mcstrans
>
> The "master" branch contains the code that was in the SRPM file that Joe
> posted to this list in June. If you have more recent changes send them
> my way and I will update the repo to include them.
>
> The "color-ewalsh" branch contains the color code for the proposal
> above. There have been some changes, namely:
>
> The format of the returned string is now hex digits with hash marks,
> e.g. "#000000 #ffffff #000000 #ffffff..."
> The separate "level" and "category" rules have been dropped and replaced
> by a single "range" rule. The SELinux interface does not expose the
> details of the MLS component of the security context. The only function
> offered is a "dominance" check implemented as a permission bit on the
> "context" security class (and even this doesn't currently work
> correctly, because it only accepts domains as the subject context, more
> on this in another post). Whether the details, which would include the
> ebitmaps for categories and level numbers, should be exposed is up for
> debate. Because of this only eight colors are now returned
A screen shot of a sample application that uses the color translations
can be seen at:
http://people.freedesktop.org/~ewalsh/mcscolor_screenshot.png
--
Eamon Walsh <ewalsh@tycho.nsa.gov>
National Security Agency
--
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:[~2008-12-06 1:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 3:59 [RFC] Add color translation support to mcstransd Eamon Walsh
2008-11-22 4:22 ` Joe Nall
2008-11-24 19:25 ` Eamon Walsh
2008-12-05 22:16 ` Xavier Toth
2008-12-06 0:31 ` Eamon Walsh
2008-12-06 1:12 ` Eamon Walsh [this message]
2008-12-06 3:41 ` Russell Coker
2008-12-08 19:47 ` Eamon Walsh
2008-12-11 21:35 ` Eamon Walsh
2008-12-24 16:23 ` Xavier Toth
2009-01-01 0:01 ` Eamon Walsh
2009-01-05 22:49 ` Daniel J Walsh
2008-12-17 16:50 ` Xavier Toth
2008-12-18 20:14 ` Eamon Walsh
2008-12-19 15:24 ` Xavier Toth
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=4939D171.5090705@tycho.nsa.gov \
--to=ewalsh@tycho.nsa.gov \
--cc=joe@nall.com \
--cc=jwcart2@tycho.nsa.gov \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=txtoth@gmail.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.