All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux Mail List <selinux@tycho.nsa.gov>,
	Joshua Brindle <jbrindle@tresys.com>
Subject: Re: [PATCH] add selpolgen
Date: Thu, 18 Jan 2007 14:53:11 -0500	[thread overview]
Message-ID: <45AFD027.9070007@mentalrootkit.com> (raw)
In-Reply-To: <1169135113.22731.285.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Tue, 2007-01-16 at 10:26 -0500, 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?
> 
> The top-level location seems sane, but the naming and structure diverges
> from the C libraries (e.g. one might expect a libsepolgen with man,
> include, src, and tests subdirectories and ChangeLog, COPYING, Makefile,
> and VERSION files).

* libsepolgen would not match python practice (this is a module not a 
library in python terms). I don't feel strongly either way, though, and 
the new patch changes this libselgen (see below).

* For python src / include are the same thing, which is why they are in 
a single directory. I put both the module directory and share under src.

* There shouldn't be man pages since doc strings and the built-in 
help(modulename) in python replace those (and the current code contains 
a fair amount of that documentation).

* I added a COPYING file and ChangeLog (empty for now).

* There is already a Makefile and VERSION and the Makefile follows the 
current conventions.

   I don't know what python libraries generally look
> like.  selpolgen is also a bit confusing with MITRE's tool, although
> that may not be important as it seems OBE.  You could just call it
> libmadison unless there is a conflict.
> 

I was trying to use a name that described its use without confusing it 
with polgen. What about 'selgen'? Any other ideas (I'd really prefer a 
meaningful name).

>> * Should the old audit2allow be retained in any form? I've tried to make 
>> this a drop-in replacement, but there are likely regressions / changes. 
>> There are also a few options still missing that I will add soon.
> 
> Unless there is a significant regression, I'd advocate just dropping the
> old one (and also finally removing audit2allow.perl, the original perl
> version that was moved aside when the python rewrite was merged).
> 

Ok. Updated patch can be found at 
http://people.redhat.com/kmacmill/patches/selinux/selgen-initial-submission.patch.gz

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-18 19:53 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
2007-01-18 15:45 ` Stephen Smalley
2007-01-18 19:53   ` Karl MacMillan [this message]
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=45AFD027.9070007@mentalrootkit.com \
    --to=kmacmillan@mentalrootkit.com \
    --cc=jbrindle@tresys.com \
    --cc=sds@tycho.nsa.gov \
    --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.