All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@tresys.com>
To: selinux@tycho.nsa.gov
Cc: selinux-dev@tresys.com
Subject: Re: (ANN: SELinux Policy Modules) announcement dealy
Date: Wed, 08 Dec 2004 14:27:02 -0500	[thread overview]
Message-ID: <41B75586.2010005@tresys.com> (raw)
In-Reply-To: <41B753E3.70805@tresys.com>

Obviously I forgot to change the subject of this email to ANN: SELinux 
Policy Modules

Joshua Brindle

Joshua Brindle wrote:

> An updated release of the binary policy module infrastructure is
> available from http://www.tresys.com/selinux/. The binary policy module
> project aims to ease policy management by developing tools for creating
> binary policy modules that can be safely linked together on a production
> system to create a system policy. To the end user, managing binary
> policy modules will be similar to managing software with a binary
> package manager like RPM. More information can be found on the website.
>
> This infrastructure includes a module compiler (checkmodule) and a set
> of programs for policy management (semodule_link, semodule_expand, and
> semodule).
>
> This release is experimental and is not intended for production use. It
> is being released to generate community feedback and discussion. For
> information on using semodule please refer to the README.MODULE file in
> selinux-doc.
>
> Joshua Brindle
> Tresys Technology
>


--
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.

      reply	other threads:[~2004-12-08 19:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 19:20 announcement dealy Joshua Brindle
2004-12-08 19:27 ` 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=41B75586.2010005@tresys.com \
    --to=jbrindle@tresys.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.