All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Joy Latten <latten@austin.ibm.com>,
	selinux@tycho.nsa.gov, dvelarde@us.ibm.com,
	selinux-dev@tresys.com
Subject: Re: writing refpolicy modules...
Date: Mon, 06 Feb 2006 14:20:28 -0500	[thread overview]
Message-ID: <43E7A17C.4050708@redhat.com> (raw)
In-Reply-To: <1139253115.31135.150.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Mon, 2006-02-06 at 13:49 -0500, Stephen Smalley wrote:
>   
>> On Mon, 2006-02-06 at 12:09 -0600, Joy Latten wrote:
>>     
>>> We (Deb and I) have a few questions in regards to creating new modules
>>> within refpolicy architecture. We have installed FC5-Test2 and we
>>> are converting old policy to the new refpolicy format.
>>>
>>> Is it ok to use the selinux-policy source rpm from rawhide as
>>> a source tree to build a refpolicy module? I understand that the
>>> necessary headers to build independent of source are not yet available.
>>>       
>> Looks like there is a selinux-policy-devel in rawhide.  Installs
>> under /usr/share/selinux/refpolicy.  So it might be worth updating to
>> the rawhide selinux-policy and installing selinux-policy-devel to try it
>> out.
>>     
>
> Looks like there is a simple policygentool script
> under /usr/share/selinux/refpolicy that can be used to generate a
> stub .te, .fc, and .if file for a new module/domain (although I assume
> that it is a mistake that the module name is left as TEMPLATE in the
> generated file), and then you can run make on the Makefile in that
> directory to generate a policy module package.  At which point you can
> insert it via semodule -i.
>
>   
http://fedoraproject.org/wiki/SELinux/FAQ/ProposedAdditions

Has a description of how to use selinux-policy-devel  The TEMPLATE 
should be TEMPLATETYPE,
which will be in RawHide tonight.

Now I would like to write a audit2allow extension to look for matches in 
/usr/share/selinux/refpolicy and use these macros rather then straight 
audit rules.


Dan



--
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:[~2006-02-06 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 18:09 writing refpolicy modules Joy Latten
2006-02-06 18:49 ` Stephen Smalley
2006-02-06 19:11   ` Stephen Smalley
2006-02-06 19:20     ` Daniel J Walsh [this message]
2006-02-06 21:35       ` Karl MacMillan

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=43E7A17C.4050708@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=dvelarde@us.ibm.com \
    --cc=latten@austin.ibm.com \
    --cc=sds@tycho.nsa.gov \
    --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.