From: James Carter <jwcart2@tycho.nsa.gov>
To: selinux@tycho.nsa.gov
Subject: Re: secilc bug
Date: Mon, 04 May 2015 11:19:51 -0400 [thread overview]
Message-ID: <55478E17.8040609@tycho.nsa.gov> (raw)
In-Reply-To: <20150503105045.GB13244@x131e>
[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]
On 05/03/2015 06:50 AM, Dominick Grift wrote:
> On Sat, May 02, 2015 at 05:02:59PM +0200, Dominick Grift wrote:
>> Today i hit an bug in secilc, when compiled by policy with some modules excluded.
>
> <snip>
>
> I suspect the issue is something like the following:
>
> There are currently no rules associated with the pam_auth_config_object_type type attribute thus it will be removed from the policy by secilc
>
> However this may or may not change. I do have macros with rules assoc. with pam_auth_config_object_type, they are currently just not called by anything
>
> In my policy, the pam_auth_config_object_type type attribute currently only acts as a bridge to auth_object_type type attribute
>
> Example: pam_config_t (and many other types) is/are assoc. with auth_pam_config_object_type, auth_pam_config_object_type is associated
> with auth_object_type, and there are rules assoc. with auth_object_type
>
> (for example: auth_admin_subject_type auth_object_type (all_file_objects (all_file_perms_except)))
>
> The question remains, how does me exluding the xserver.cil affects all this. I actually commented out the only call to
> the auth.cil module ( (call auth_pam_config_object_type (xserver_pam_config_t)) ) from the xserver module and it turns out to not
> affect it. So it is not that macro call.
>
> It may instead be another ordering issue...
>
There doesn't seem to be ordering issues related to typeattributeset statements.
See attached test policy if you're interested.
> E.g. excluding the xserver.cil module may mess up the ordering of the modules to process in such a way that this rule vanishes
>
> Because that is what this issue boils down to: rules vanishing for no reason
>
> I made a screencast that tries to explain the issue:
>
> https://www.youtube.com/watch?v=XRp5z9aqLDo
>
>
I think that it would be more helpful to me if I could see the policy. Is it
available anywhere? If not, could you send me at least the auth.cil and
xserver.cil modules?
--
James Carter <jwcart2@tycho.nsa.gov>
National Security Agency
[-- Attachment #2: test.cil --]
[-- Type: application/vnd.ms-artgalry, Size: 1827 bytes --]
next prev parent reply other threads:[~2015-05-04 15:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 2:49 [GIT PULL] SELinux patches for 4.1 Paul Moore
2015-04-02 12:32 ` James Morris
2015-04-02 21:18 ` Paul Moore
2015-04-03 2:45 ` James Morris
2015-04-03 9:04 ` Paul Moore
2015-04-03 15:07 ` James Morris
2015-04-03 22:22 ` Paul Moore
2015-04-04 0:49 ` James Morris
2015-04-04 2:36 ` Paul Moore
2015-04-05 23:14 ` James Morris
2015-04-06 12:48 ` Paul Moore
2015-04-06 14:04 ` James Morris
2015-04-06 14:09 ` James Morris
2015-04-07 0:43 ` Paul Moore
2015-04-08 10:57 ` James Morris
2015-04-08 11:04 ` Paul Moore
2015-04-13 1:46 ` James Morris
2015-04-23 22:06 ` Paul Moore
2015-04-24 0:24 ` James Morris
2015-04-24 14:53 ` Paul Moore
2015-04-24 16:20 ` Casey Schaufler
2015-04-26 21:22 ` Paul Moore
2015-04-27 5:28 ` James Morris
2015-04-28 23:53 ` Mimi Zohar
2015-05-02 15:03 ` secilc bug Dominick Grift
2015-05-03 10:50 ` Dominick Grift
2015-05-04 15:19 ` James Carter [this message]
2015-05-04 15:33 ` Steve Lawrence
2015-05-04 15:44 ` Dominick Grift
2015-05-04 15:46 ` Dominick Grift
2015-05-04 15:37 ` Dominick Grift
2015-08-03 19:21 ` Dominick Grift
2015-04-27 5:28 ` [GIT PULL] SELinux patches for 4.1 James Morris
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=55478E17.8040609@tycho.nsa.gov \
--to=jwcart2@tycho.nsa.gov \
--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.