From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Catalin DIMA <dima@univ-paris12.fr>
Cc: selinux@tycho.nsa.gov, Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: Problems installing current version of refpolicy with FC6
Date: Mon, 29 Jan 2007 16:35:59 -0500 [thread overview]
Message-ID: <45BE68BF.3030607@mentalrootkit.com> (raw)
In-Reply-To: <45BE6262.5080902@univ-paris12.fr>
Catalin DIMA wrote:
> Karl MacMillan wrote:
>
>> Just to check - are you certain that you want the full policy? You may
>> be able to do the teaching you need with policy modules only.
>
> Do you mean I should compile&load the modular policy ? I certainly would
> like to do this, as it's supposed to be easily configurable & suitable
> for experimenting small modules.
>
>> Did you enable mcs? The standard FC6 policy is targeted-mcs and the
>> presence of the mcs components in the file system labels may be the
>> cause of your problems.
>
> I tried again this build.conf format :
>
> TYPE = targeted-mcs
> NAME = refpolicy
> DISTRO = redhat
> DIRECT_INITRC=n
> MONOLITHIC=n
> MLS-SENS=16
> MLS_CATS=256
>
> Done make conf, make install and make load, then configured for
> refpolicy & asked for relabeling, and the system gets stuck...
>
Could you elaborate on where it gets stuck. Does the labeling happen?
You might try relabeling in permissive.
> Btw, forgot to mention the libsepol.sepol_genbools: error while reading
> /etc/selinx/refpolicy/booleans error...
>
In permissive or enforcing?
> In permissive refpolicy mode, the only selinux message talks about
> NetworkManager.
>
Just to clarify, things work fine in permissive mode and you are only
getting a single AVC message, correct? Could you check /var/log/messages
and /var/log/audit/audit.log for avc messages after a permissive boot.
Also check the selinux messages in dmesg for errors.
>> The unknown boolean messages should be harmless I believe.
>>
>> You can extract the build.conf from the policy source rpm as well,
>> which is likely a good starting point.
>
> The problem is the same with the rpm and the bz2...
>
Not certain what you mean here - the source rpm or the binary rpm? I was
suggesting that you rebuild refpolicy using the configuration from the
source rpm - which means extracting the correct build.conf,
modules.conf, and booleans.conf, seusers, and users_extra files and
installing the in the source tree. You can read the spec file to see how
this is done during the build process.
Dan - do you have better directions on how to get a patched and
configured refpolicy tree out of the source rpm?
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.
next prev parent reply other threads:[~2007-01-29 21:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 19:03 Problems installing current version of refpolicy with FC6 Catalin DIMA
2007-01-29 19:49 ` Karl MacMillan
2007-01-29 21:08 ` Catalin DIMA
2007-01-29 21:35 ` Karl MacMillan [this message]
2007-01-29 23:24 ` Catalin DIMA
2007-01-30 14:52 ` Karl MacMillan
2007-02-02 16:15 ` DWARF2 [was : Problems installing refpolicy with FC6] Catalin DIMA
2007-02-02 17:02 ` Paul Moore
2007-02-02 17:29 ` Catalin DIMA
2007-02-05 15:34 ` Problems installing current version of refpolicy with FC6 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=45BE68BF.3030607@mentalrootkit.com \
--to=kmacmillan@mentalrootkit.com \
--cc=dima@univ-paris12.fr \
--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.