From: Steve Lawrence <slawrence@tresys.com>
To: Miroslav Grepl <mgrepl@redhat.com>, SELinux <selinux@tycho.nsa.gov>
Subject: Re: CIL: migrate_store issues with MLS policy
Date: Thu, 21 May 2015 11:36:09 -0400 [thread overview]
Message-ID: <555DFB69.1010802@tresys.com> (raw)
In-Reply-To: <555DEECA.1010409@redhat.com>
On 05/21/2015 10:42 AM, Miroslav Grepl wrote:
> We try to get working Fedora SELinux policy builds with migrated store.
> But we get some issues with MLS policy. We needed to add the following
> fixes to make it working.
>
> https://github.com/mgrepl/selinux-policy/commit/daad0252400284027e8a5c300addf6226f74e312
Looks like a bug with the pp2cil converter. Looking into this.
> and
>
> https://github.com/mgrepl/selinux-policy/commit/113792a78ac27e8a05b4e3b550d7bc40c3c937db
>
This works for staff_r, user_r, and sysadm_r because of this hack:
https://github.com/SELinuxProject/selinux/blob/master/libsepol/src/module_to_cil.c#L2023-L2045
The issue here is that secadm and auditadm are always defined in their
respective modules, but conditionally defined in base if enable_mls is
true. Because of this, we can't really use the hack mentioned above,
because auditadm_r and secamd_r aren't always in base, which that hack
relies on.
It's possible we could do the reverse of that for these roles, and only
declare secadm_r and auditadm_r when NOT converting a base module. But I
this could potentially break things if enable_mls == true and
auditadm/secadm modules aren't installed, but something still relies on
the roles. Not immediately clear if that's the case. Will have to look
into this...
> Please check my commit messages.
>
> Regards,
> Miroslav
>
next prev parent reply other threads:[~2015-05-21 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 14:42 CIL: migrate_store issues with MLS policy Miroslav Grepl
2015-05-21 15:36 ` Steve Lawrence [this message]
2015-05-21 15:51 ` Miroslav Grepl
2015-05-22 15:41 ` Steve Lawrence
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=555DFB69.1010802@tresys.com \
--to=slawrence@tresys.com \
--cc=mgrepl@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.