From: Paul Moore <paul.moore@hp.com>
To: TaurusHarry <harrytaurus2002@hotmail.com>
Cc: selinux-mailing-list <selinux@tycho.nsa.gov>,
refpolicy-mailing-list <refpolicy@oss1.tresys.com>
Subject: Re: Problem about audit-test-2090 + refpolicy-2.20091117
Date: Wed, 18 Aug 2010 07:52:47 -0400 [thread overview]
Message-ID: <1282132367.4122.8.camel@flek> (raw)
In-Reply-To: <SNT139-w318948F5C7E5124B30AB6AAB9D0@phx.gbl>
On Wed, 2010-08-18 at 10:26 +0000, TaurusHarry wrote:
> Hi SELinux exports,
>
> When I am trying to build the lspp_test.pp provided by
> audit-test-2090/utils/selinux-policy/lspp_test.* along with the
> refpolicy-20091117 source code, I copied lspp_test.* files to
> policy/modules/apps/ and then modified policy/modules.conf to declare
> "lspp_test = module", but I run into below error message ...
Is there any reason why you copied the lspp_test policy files to the
refpolicy sources and tried to build it there? I'm not completely sure
that this is the cause of your problem but I can say for certain that
this is not a tested procedure for building the lspp_test module.
The normal procedure is to build the lspp_test policy module separately
from the system's main SELinux policy, e.g. build and install the normal
system's SELinux policy (refpolicy-20091117 in your case) and after you
have verified that everything is working correctly you can change to the
directory audit-test-*/utils/selinux-policy directory and use the
Makefile located their to build the lspp_test module.
--
paul moore
linux @ hp
--
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.
WARNING: multiple messages have this Message-ID (diff)
From: paul.moore@hp.com (Paul Moore)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Problem about audit-test-2090 + refpolicy-2.20091117
Date: Wed, 18 Aug 2010 07:52:47 -0400 [thread overview]
Message-ID: <1282132367.4122.8.camel@flek> (raw)
In-Reply-To: <SNT139-w318948F5C7E5124B30AB6AAB9D0@phx.gbl>
On Wed, 2010-08-18 at 10:26 +0000, TaurusHarry wrote:
> Hi SELinux exports,
>
> When I am trying to build the lspp_test.pp provided by
> audit-test-2090/utils/selinux-policy/lspp_test.* along with the
> refpolicy-20091117 source code, I copied lspp_test.* files to
> policy/modules/apps/ and then modified policy/modules.conf to declare
> "lspp_test = module", but I run into below error message ...
Is there any reason why you copied the lspp_test policy files to the
refpolicy sources and tried to build it there? I'm not completely sure
that this is the cause of your problem but I can say for certain that
this is not a tested procedure for building the lspp_test module.
The normal procedure is to build the lspp_test policy module separately
from the system's main SELinux policy, e.g. build and install the normal
system's SELinux policy (refpolicy-20091117 in your case) and after you
have verified that everything is working correctly you can change to the
directory audit-test-*/utils/selinux-policy directory and use the
Makefile located their to build the lspp_test module.
--
paul moore
linux @ hp
next prev parent reply other threads:[~2010-08-18 11:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 10:26 Problem about audit-test-2090 + refpolicy-2.20091117 TaurusHarry
2010-08-18 10:26 ` [refpolicy] " TaurusHarry
2010-08-18 11:52 ` Paul Moore [this message]
2010-08-18 11:52 ` Paul Moore
2010-08-18 13:24 ` TaurusHarry
2010-08-18 13:24 ` [refpolicy] " TaurusHarry
2010-08-18 13:38 ` Dominick Grift
2010-08-18 13:43 ` Dominick Grift
2010-08-18 15:29 ` Paul Moore
2010-08-18 15:29 ` [refpolicy] " Paul Moore
2010-08-19 12:54 ` Christopher J. PeBenito
2010-08-19 12:54 ` Christopher J. PeBenito
2010-08-19 12:58 ` Christopher J. PeBenito
2010-08-19 12:58 ` 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=1282132367.4122.8.camel@flek \
--to=paul.moore@hp.com \
--cc=harrytaurus2002@hotmail.com \
--cc=refpolicy@oss1.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.