From: Joshua Brindle <jbrindle@tresys.com>
To: Steve G <linux_4ever@yahoo.com>
Cc: selinux@tycho.nsa.gov, selinux-dev@tresys.com
Subject: Re: ANN: SELinux Policy Server Project
Date: Wed, 15 Dec 2004 10:15:16 -0500 [thread overview]
Message-ID: <1103123717.758.4.camel@twoface> (raw)
In-Reply-To: <20041215144654.34582.qmail@web50602.mail.yahoo.com>
This is just the project announcement and a very preliminary release.
There is no daemon yet, what this release provides is the initial
support for hierarchal policy structure and a way to verify the policy.
This is an important first step to being able to refer to yet-unknown
parts of the policy for access control.
In selinux-doc/README.MODULES there are instructions for using the
hierarchy checker with the semodule framework.
Joshua Brindle
On Wed, 2004-12-15 at 06:46 -0800, Steve G wrote:
> Hi,
>
> >We at Tresys have started a project to design and implement an
> >SELinux policy server.
>
> Simple question...when I untar the source, where exactly is the source code for
> the daemon? I'll give it a going over.
>
> Thanks,
> -Steve Grubb
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
--
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:[~2004-12-15 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041210162047.HHLP7908.mm-ismta4.bizmailsrvcs.net@FLM800>
2004-12-13 20:45 ` ANN: SELinux Policy Server Project Joshua Brindle
2004-12-15 14:46 ` Steve G
2004-12-15 15:15 ` Joshua Brindle [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=1103123717.758.4.camel@twoface \
--to=jbrindle@tresys.com \
--cc=linux_4ever@yahoo.com \
--cc=selinux-dev@tresys.com \
--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.