From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Hung Truong <hung.truong@tridsys.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: Turn off "dontaudit" rules in monolithic policy
Date: Tue, 22 Jan 2013 13:02:39 -0500 [thread overview]
Message-ID: <50FED43F.9030909@tresys.com> (raw)
In-Reply-To: <3086262d0228a121663cb87f5d77a07a@mail.gmail.com>
To clarify terminology, if you're using semodule, you're using a modular policy, not a monolithic policy. A monolithic policy would be fully compiled on the development machine, and the policy.27 would be deployed to the running machine. A modular policy deploys the *.pp files to the running machine and links them together to make a policy.27.
On 01/21/13 12:25, Hung Truong wrote:
> I have a custom monolithic build based on RHEL6 policy.
> I get this error when try to turn off dontaudit rules:
>
> $ semodule -DB
>
>
> libsemanage.semanage_link_sandbox: Could not access sandbox base file /etc/selinux/targeted/modules/bmp/base.pp. (No such file or directory)
>
> Is there other way to turn off dontaudit rules in a monilithic policy?
>
>
>
> Many thanks,
>
> --Hung Truong
>
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
--
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:[~2013-01-22 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 17:25 Turn off "dontaudit" rules in monolithic policy Hung Truong
2013-01-22 14:19 ` Vu, Joseph
2013-01-22 14:31 ` Hung Truong
2013-01-22 15:10 ` Daniel J Walsh
2013-01-22 15:14 ` Hung Truong
[not found] ` <50FEAEE1.9000002@redhat.com>
2013-01-22 16:54 ` Hung Truong
2013-01-22 18:02 ` Christopher J. PeBenito [this message]
2013-01-22 18:12 ` Hung Truong
2013-01-22 18:20 ` Christopher J. PeBenito
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=50FED43F.9030909@tresys.com \
--to=cpebenito@tresys.com \
--cc=hung.truong@tridsys.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.