From: Paul Moore <paul.moore@hp.com>
To: TaurusHarry <harrytaurus2002@hotmail.com>
Cc: selinux-mailing-list <selinux@tycho.nsa.gov>, refpolicy@oss1.tresys.com
Subject: RE: Problem about audit-test-2090 + refpolicy-2.20091117
Date: Wed, 18 Aug 2010 11:29:53 -0400 [thread overview]
Message-ID: <1282145393.4122.45.camel@flek> (raw)
In-Reply-To: <SNT139-w499FFC8245BD574722F9F6AB9D0@phx.gbl>
On Wed, 2010-08-18 at 13:24 +0000, TaurusHarry wrote:
> Many many thanks for your response!
>
> Well, after I installed SELinux header properly then I did could enter
> audit-test/utils/selinux-policy/ successfully built lspp_test.pp
> there, however, I run into below error messages when trying to insert
> it:
>
> [root/secadm_r/s0@qemu-host selinux-policy]# semodule -i lspp_test.pp
> libsepol.expand_terule_helper: conflicting TE rule for
> ( lspp_test_generic_t, sepgsql_db_t:db_table): old was
> user_sepgsql_table_t, new is sepgsql_table_t
> libsepol.expand_module: Error during expand
> libsemanage.semanage_expand_sandbox: Expand module failed
> semodule: Failed!
> [root/secadm_r/s0@qemu-host selinux-policy]#
>
> Very honestly speaking I am clueless about such error message, so I
> tried to compile lspp_test.pp along with refpolicy source code just to
> see if such problem could simply disappear. Do you have some comments
> or suggestions about it?
Hmm, it looks like perhaps there is a conflict with the sepostgres
policy? I'm not sure, I haven't built this policy on recent versions of
the refpolicy. I've heard rumors that some of the RH guys are running
audit-test on recent versions of Fedora/RHEL6 but I don't know if that
includes all of the LSPP bits, e.g. the lspp_test policy module.
If you want to play with SELinux policy, we're always accepting
patches :)
> Moreover, the audit-test-2090 seems to be a little "old" than the
> refpolicy-2.20091117, for example, the lspp_test.te calls
> mls_file_read_up() rather than the expected
> mls_file_read_all_levels(), do you know if I could find some latest
> version of audit-test package or some latest version of the
> lspp_test.* files?
You can always find the latest bits in the audit-test SVN repo on
sf.net, however, I must admit that currently we've only tested it
against RHEL5.x and some older Fedora releases.
--
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 11:29:53 -0400 [thread overview]
Message-ID: <1282145393.4122.45.camel@flek> (raw)
In-Reply-To: <SNT139-w499FFC8245BD574722F9F6AB9D0@phx.gbl>
On Wed, 2010-08-18 at 13:24 +0000, TaurusHarry wrote:
> Many many thanks for your response!
>
> Well, after I installed SELinux header properly then I did could enter
> audit-test/utils/selinux-policy/ successfully built lspp_test.pp
> there, however, I run into below error messages when trying to insert
> it:
>
> [root/secadm_r/s0 at qemu-host selinux-policy]# semodule -i lspp_test.pp
> libsepol.expand_terule_helper: conflicting TE rule for
> ( lspp_test_generic_t, sepgsql_db_t:db_table): old was
> user_sepgsql_table_t, new is sepgsql_table_t
> libsepol.expand_module: Error during expand
> libsemanage.semanage_expand_sandbox: Expand module failed
> semodule: Failed!
> [root/secadm_r/s0 at qemu-host selinux-policy]#
>
> Very honestly speaking I am clueless about such error message, so I
> tried to compile lspp_test.pp along with refpolicy source code just to
> see if such problem could simply disappear. Do you have some comments
> or suggestions about it?
Hmm, it looks like perhaps there is a conflict with the sepostgres
policy? I'm not sure, I haven't built this policy on recent versions of
the refpolicy. I've heard rumors that some of the RH guys are running
audit-test on recent versions of Fedora/RHEL6 but I don't know if that
includes all of the LSPP bits, e.g. the lspp_test policy module.
If you want to play with SELinux policy, we're always accepting
patches :)
> Moreover, the audit-test-2090 seems to be a little "old" than the
> refpolicy-2.20091117, for example, the lspp_test.te calls
> mls_file_read_up() rather than the expected
> mls_file_read_all_levels(), do you know if I could find some latest
> version of audit-test package or some latest version of the
> lspp_test.* files?
You can always find the latest bits in the audit-test SVN repo on
sf.net, however, I must admit that currently we've only tested it
against RHEL5.x and some older Fedora releases.
--
paul moore
linux @ hp
next prev parent reply other threads:[~2010-08-18 15:30 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
2010-08-18 11:52 ` [refpolicy] " 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 [this message]
2010-08-18 15:29 ` 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=1282145393.4122.45.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.