From: Daniel J Walsh <dwalsh@redhat.com>
To: Steve Lawrence <slawrence@tresys.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Cc: Joshua Brindle <jbrindle@tresys.com>, SELinux <selinux@tycho.nsa.gov>
Subject: Re: Been looking at further shrinkage of the SELinux footprint on Linux.
Date: Thu, 31 Oct 2013 14:48:20 -0400 [thread overview]
Message-ID: <5272A5F4.7040108@redhat.com> (raw)
In-Reply-To: <52725064.4080508@tresys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/31/2013 08:43 AM, Steve Lawrence wrote:
> On 10/30/2013 04:47 PM, Stephen Smalley wrote:
>> On 10/30/2013 04:43 PM, Stephen Smalley wrote:
>>> On 10/30/2013 04:36 PM, Daniel J Walsh wrote:
>>>> Well we have done some work on combining like domains, see antivirus
>>>> and spamassassin, but this is a lot of work which no one has time
>>>> for.
>>>>
>>>> I would love to see the mailserver and mailclients domains combined.
>>>>
>>>> If people want to suggest or more importantly submit patches to
>>>> combine other domains, I am all for it.
>>>>
>>>> Problems with shipping policy within rpm still exists. although we
>>>> (Red Hat) are at least moving toward layered products shipping their
>>>> own policy. openstack-selinux, openshift-selinux, gluster-selinux.
>>>> This is more for them updating quicker then RHEL.
>>>>
>>>> 1. semanage is slowwwwwwwww. If we ran all pp files without
>>>> combining them into a single transaction the installation and yum
>>>> updates would take a long time.
>>>
>>> Yes, I have to wonder if we don't need a complete overhaul/replacement
>>> of libsemanage (+ module portions of libsepol). It seems like
>>> semodule/semanage transactions are far slower than running the entire
>>> policy through checkpolicy again (i.e. just using source modules and
>>> running them through m4 + checkpolicy on each transaction, ala the
>>> source policy module work that sadly has yet to reach
>>> maturity/completion).
>>
>> However, on this note, I'm pretty sure that the rpm work allows you to
>> just collect up all of the policy modules and run semodule once at the
>> end (collections or whatever). So that particular problem should be
>> solved already even for the binary modules.
>>
>
> This is correct. the collection feature of RPM gathers up all selinux
> policies from all the rpms in the yum/rpm transaction and installs them all
> in a single semanage transaction. Note that although the work was
> upstreamed, last I checked, the building of the selinux plugin that
> performs the work to aggregate and install the policy modules is currently
> disabled on fedora.
>
>>>
>>>> 2. Cordination between domains, we put a fix into an interface and
>>>> we need to trigger 10 packages to update.
>>>>
>>>> For every apache bug in policy, do we want to wait for an update
>>>> apache package, or do we ship lots more packages.
>>>
>>> That's also fixed if we go with source modules, right, since interface
>>> change would get applied by the m4 + checkpolicy cycle. Or CIL.
>>>
>>>> 3. Uninstall of types leaves unlabeled_t content on disk.
>>>
>>> That's the only one that seems fundamental. What if we pushed all
>>> file type declarations into their own module linked to the base
>>> filesystem package and just always installed that? That won't affect
>>> policy size substantially; it is the allow rules that are the issue
>>> IIUC, not just the type decls.
>>>
>
> The way this is handled in the RPM collection feature is modules are never
> uninstalled, even if the package that installed that module is. Not ideal,
> but it solves this problem.
>
>
> -- 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.
Can you open a bugzilla on this, and show me point me at documentation on how
to use this.
In current Fedora we are attempting to ship a binary policy precompiled so we
do not take a long time/memory in initial install. But it would be nice to
tell people to use the new feature to run their policy load in a transaction.
It would also be nice if we could do semanage commands within this transaction.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlJypfQACgkQrlYvE4MpobOYvgCeKNApBdzF79GRlgxylcyacwGp
siQAoKdnXhyIa/x1ezXb0bMKCA0ZoOjq
=oReg
-----END PGP SIGNATURE-----
--
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.
next prev parent reply other threads:[~2013-10-31 18:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 19:31 Been looking at further shrinkage of the SELinux footprint on Linux Daniel J Walsh
2013-10-30 19:42 ` Joshua Brindle
2013-10-30 20:14 ` Stephen Smalley
2013-10-30 20:36 ` Daniel J Walsh
2013-10-30 20:43 ` Stephen Smalley
2013-10-30 20:47 ` Stephen Smalley
2013-10-31 12:43 ` Steve Lawrence
2013-10-31 12:56 ` Stephen Smalley
2013-10-31 18:52 ` Daniel J Walsh
2013-11-06 23:34 ` Timothée Ravier
2013-10-31 18:48 ` Daniel J Walsh [this message]
2013-11-02 16:42 ` Sven Vermeulen
2013-11-02 18:09 ` Casey Schaufler
2013-11-02 21:18 ` Joshua Brindle
2013-11-04 14:42 ` Daniel J Walsh
2013-11-06 15:35 ` Sven Vermeulen
2013-11-06 15:40 ` Daniel J Walsh
2013-10-30 22:01 ` Colin Walters
2013-10-31 11:30 ` Stephen Smalley
2013-10-30 23:54 ` Colin Walters
2013-10-31 18:27 ` Daniel J Walsh
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=5272A5F4.7040108@redhat.com \
--to=dwalsh@redhat.com \
--cc=jbrindle@tresys.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=slawrence@tresys.com \
/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.