All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Paul Moore <paul.moore@hp.com>
Cc: TaurusHarry <harrytaurus2002@hotmail.com>,
	refpolicy@oss1.tresys.com,
	selinux-mailing-list <selinux@tycho.nsa.gov>
Subject: Re: [refpolicy] Problem about audit-test-2090 + refpolicy-2.20091117
Date: Thu, 19 Aug 2010 08:54:44 -0400	[thread overview]
Message-ID: <4C6D2994.6060109@tresys.com> (raw)
In-Reply-To: <1282145393.4122.45.camel@flek>

On 08/18/10 11:29, Paul Moore wrote:
> 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?

Yep, there are conflicting type_transitions.  Basically it is 
complaining about these two rules:

type_transition lspp_test_generic_t sepgsql_db_t:db_table 
user_sepgsql_table_t;

type_transition lspp_test_generic_t sepgsql_db_t:db_table sepgsql_table_t;

so it fails.

-- 
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.

WARNING: multiple messages have this Message-ID (diff)
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Problem about audit-test-2090 + refpolicy-2.20091117
Date: Thu, 19 Aug 2010 08:54:44 -0400	[thread overview]
Message-ID: <4C6D2994.6060109@tresys.com> (raw)
In-Reply-To: <1282145393.4122.45.camel@flek>

On 08/18/10 11:29, Paul Moore wrote:
> 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?

Yep, there are conflicting type_transitions.  Basically it is 
complaining about these two rules:

type_transition lspp_test_generic_t sepgsql_db_t:db_table 
user_sepgsql_table_t;

type_transition lspp_test_generic_t sepgsql_db_t:db_table sepgsql_table_t;

so it fails.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  reply	other threads:[~2010-08-19 12:54 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
2010-08-18 15:29       ` [refpolicy] " Paul Moore
2010-08-19 12:54       ` Christopher J. PeBenito [this message]
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=4C6D2994.6060109@tresys.com \
    --to=cpebenito@tresys.com \
    --cc=harrytaurus2002@hotmail.com \
    --cc=paul.moore@hp.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.