All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: [PATCH] add selpolgen
Date: Tue, 16 Jan 2007 11:40:49 -0500	[thread overview]
Message-ID: <1168965649.10069.11.camel@localhost.localdomain> (raw)
In-Reply-To: <45ACFC09.5000002@tresys.com>

On Tue, 2007-01-16 at 11:23 -0500, Joshua Brindle wrote:
> Karl MacMillan wrote:
> > This is a patch (available for download because of size - see url 
> > below) to add a python library named selpolgen and a new version of 
> > audit2allow that uses this library. This is a minimally changed 
> > version of what I have been calling madison.
> >
> > I am submitting this for inclusion as part of the main selinux 
> > distribution. I believe that inclusion here will help make good policy 
> > generation tools develop sooner and give a common base for creating 
> > new tools.
> >
> > Questions:
> > * I have the library at the top-level of the project - like the C 
> > libraries. Is this the best location? What about the name?
> This doesn't seem like a good place, and the upstream selinux repo 
> doesn't seem like a good dumping ground for all-things-selinux either, I 
> don't know of a better way to spur community support though.
> 

This is certainly not dumping a random selinux-related project into the
upstream repo. If you look at the code there is:

1) A replacement for audit2allow - obviously this was deemed relevant at
some point so I don't see why an improved version would not still be
relevant.

2) A well-structured python library that includes many useful features
(parsing audit messages, creating / compiling modules, generating
selinux policy, etc.) with very little overlap to the other libraries
(the main overlap is parsing - which I am actively working on merging
with libsepol / checkpolicy).

I believe that what is added in 2 is truly generally useful for selinux
related applications. Additionally, by including this code I don't that
that upstream is automatically obligated to accept any new applications
based on this.

Karl


--
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:[~2007-01-16 16:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-16 15:26 [PATCH] add selpolgen Karl MacMillan
2007-01-16 16:23 ` Joshua Brindle
2007-01-16 16:40   ` Karl MacMillan [this message]
2007-01-18 15:45 ` Stephen Smalley
2007-01-18 19:53   ` Karl MacMillan
2007-01-19 13:49     ` Stephen Smalley
2007-01-19 16:09       ` Stephen Smalley
2007-01-19 16:23         ` Karl MacMillan
2007-01-19 16:59           ` Stephen Smalley
2007-01-19 17:08             ` Karl MacMillan
2007-01-19 17:16             ` 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=1168965649.10069.11.camel@localhost.localdomain \
    --to=kmacmillan@mentalrootkit.com \
    --cc=jbrindle@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.