From: "Frank Mayer" <mayerf@tresys.com>
To: "'Serge E. Hallyn'" <hallyn@cs.wm.edu>,
"'selinux'" <selinux@tycho.nsa.gov>
Subject: RE: policy administration
Date: Thu, 12 Dec 2002 10:51:12 -0500 [thread overview]
Message-ID: <001601c2a1f6$57480680$6600a8c0@columbia.tresys.com> (raw)
In-Reply-To: <20021130022643.A8018@escher.cs.wm.edu>
Sorry I missed this message earlier, we are doing some work in this
area. See our web site (www.tresys.com/selinux) which has information
about released tools...within a week or two we're releasing updated
versions of our tools and a new *basic* policy browser/editor/config
tool.
Frank
> -----Original Message-----
> Behalf Of Serge E. Hallyn
> Sent: Saturday, November 30, 2002 2:27 AM
> To: selinux
> Subject: policy administration
>
> Hi,
>
> For the past, er, while, I've been working on tools for dealing
> with DTE policies. I'd now like to start applying that to selinux
> policies. Briefly, the work spanned from the extremely mundane
> (a gui policy editor) to the somewhat less mundane (presenting
> graphical representations of relations in policies) to the
> stuff I enjoyed more (constructing policies from modules, and
> analyzing policies using other MAC systems - ie using the BLP
> star-property to introduce relations on types, in a manner similar
> to what TIS did in 1998 to allow automatic policy updates*).
>
> I've been looking at the website and the mailing list, and it
> doesn't seem anyone is doing anything like this just yet. If
> anyone is, please let me know.
>
> thanks,
> -serge
--
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.
prev parent reply other threads:[~2002-12-12 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-30 7:26 policy administration Serge E. Hallyn
2002-12-12 15:51 ` Frank Mayer [this message]
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='001601c2a1f6$57480680$6600a8c0@columbia.tresys.com' \
--to=mayerf@tresys.com \
--cc=hallyn@cs.wm.edu \
--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.