From: Joshua Kramer <josh@globalherald.net>
To: selinux@tycho.nsa.gov
Subject: Re: Rebuilding Modified Base Policy on RHEL6 (was on-Computing Abstractions & An Issue Thereof)
Date: Sat, 26 Jun 2010 19:06:15 -0400 [thread overview]
Message-ID: <4C2687E7.5000705@globalherald.net> (raw)
In-Reply-To: <4C2652F3.8010309@globalherald.net>
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
> Is the method for rebuilding policy explained in the following guide,
> still effective for RHEL6?
> http://danwalsh.livejournal.com/26428.html
>
Ok, so I followed the instructions on the noted page; specifically, near
the bottom. This line works to rebuild policy on RHEL6:
*make validate UNK_PERMS=allow NAME=strict TYPE=mcs DISTRO=redhat UBAC=n
DIRECT_INITRC=y MONOLITHIC=n POLY=y MLS_CATS=1024 MCS_CATS=1024 base
However, if I do this*, to switch the build from strict to targeted:
cd ~/sources/BUILD/serefpolicy-VERSION
make UNK_PERMS=allow NAME=targeted TYPE=mcs DISTRO=redhat UBAC=n
DIRECT_INITRC=y MONOLITHIC=n POLY=y MLS_CATS=1024 MCS_CATS=1024 bare
make conf
make UNK_PERMS=allow NAME=targeted TYPE=mcs DISTRO=redhat UBAC=n
DIRECT_INITRC=y MONOLITHIC=n POLY=y MLS_CATS=1024 MCS_CATS=1024 conf
...the make breaks with this error:
Creating targeted base module base.conf
cat tmp/pre_te_files.conf tmp/all_attrs_types.conf tmp/global_bools.conf
tmp/only_te_rules.conf tmp/all_post.conf > base.conf
Compiling targeted base module
/usr/bin/checkmodule -M -U allow base.conf -o tmp/base.mod
/usr/bin/checkmodule: loading policy configuration from base.conf
policy/modules/kernel/domain.te":195:ERROR 'type selinux_config_t is not
within scope' at token ';' on line 9468:
#line 195
dontaudit domain selinux_config_t:dir { getattr search open };
/usr/bin/checkmodule: error(s) encountered while parsing configuration
make: *** [tmp/base.mod] Error 1
It breaks even with a non-modified policy (i.e. install src.rpm and run
this make command).
Do I need to do this, even if I only want to build a modified "targeted"
version of the policy? Is it "strict" by default?
Thanks,
-Josh
[-- Attachment #2: Type: text/html, Size: 2304 bytes --]
next prev parent reply other threads:[~2010-06-26 23:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 16:28 Non-Computing Abstractions & An Issue Thereof Richard Haines
2010-06-03 18:34 ` Joshua Kramer
2010-06-26 19:20 ` Rebuilding Modified Base Policy on RHEL6 (was on-Computing Abstractions & An Issue Thereof) Joshua Kramer
2010-06-26 23:06 ` Joshua Kramer [this message]
2010-06-26 23:24 ` Justin P. Mattock
2010-06-28 17:37 ` Stephen Smalley
2010-06-27 11:30 ` Dominick Grift
2010-06-28 18:13 ` 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=4C2687E7.5000705@globalherald.net \
--to=josh@globalherald.net \
--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.