From: Joshua Brindle <method@manicmethod.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: "Anamitra Dutta Majumdar (anmajumd)" <anmajumd@cisco.com>,
SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Adding AV assertion to selinux policy in RHEL5
Date: Wed, 26 Aug 2009 12:09:13 -0400 [thread overview]
Message-ID: <4A955E29.4030703@manicmethod.com> (raw)
In-Reply-To: <4A952BA3.7050401@redhat.com>
Daniel J Walsh wrote:
> On 08/25/2009 06:43 PM, Anamitra Dutta Majumdar (anmajumd) wrote:
>>
>>
>> We are looking for a well documented procedure to add AV assertion to
>> selinux policy on RHEL5.
>> So far all SELinux URL links refer to the fact that the AV assertion
>> needs to be added to assert.te file under $SELINUX_SRC folder.
>> This appears to be true only for RHEL4 not RHEL5 since there is no src
>> folder under /etc/selinux/targeted that contains the source policies in
>> RHEL5.
>> We have installed and built the selinux-policy-2.4.6-248.el5.src.rpm on
>> our RHEL5.4 box and we did not find any assert.te file.
>> Can someone help us with the exact method as to what needs to be done to
>> add an AV assertion rule to our policy.
>>
>> Thanks
>> Anamitra& Radha
>>
>> --
>> fedora-selinux-list mailing list
>> fedora-selinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/fedora-selinux-list
> questions like this should be asked on the SELinux<selinux@tycho.nsa.gov> Mail List.
>
> I am not sure what you are asking for.
assert.te was the old place for neverallow rules in the example policy. In the
reference policy neverallows are put in their appropriate place (you could grep
for them in the source policy if you want to see).
However, with RHEL5 and greater distros you can just insert policy modules to
add rules (including assertions). So just follow the RHEL5 instructions on
adding a policy and you can add neverallows there.
You also need to enable assertion checking by adding this line to
/etc/selinux/semanage.conf
expand-check = 1
--
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.
next prev parent reply other threads:[~2009-08-26 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c63e41180908211425s3a66c448g1a81865c9f14bcc@mail.gmail.com>
[not found] ` <alpine.LRH.2.00.0908241149000.21562@tundra.namei.org>
[not found] ` <4EF101F7236DB443A8FABF8164BFBD0C084801CF@xmb-sjc-223.amer.cisco.com>
2009-08-26 12:33 ` Adding AV assertion to selinux policy in RHEL5 Daniel J Walsh
2009-08-26 16:09 ` Joshua Brindle [this message]
2009-08-26 17:14 ` Daniel J Walsh
[not found] ` <4EF101F7236DB443A8FABF8164BFBD0C0850C77E@xmb-sjc-223.amer.cisco.com>
2009-08-27 20:24 ` Joshua Brindle
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=4A955E29.4030703@manicmethod.com \
--to=method@manicmethod.com \
--cc=anmajumd@cisco.com \
--cc=dwalsh@redhat.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.