All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Daniel J Walsh <dwalsh@redhat.com>
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: Wed, 30 Oct 2013 16:43:56 -0400	[thread overview]
Message-ID: <52716F8C.6060109@tycho.nsa.gov> (raw)
In-Reply-To: <52716DE6.8040401@redhat.com>

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

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




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

  reply	other threads:[~2013-10-30 20:43 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 [this message]
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
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=52716F8C.6060109@tycho.nsa.gov \
    --to=sds@tycho.nsa.gov \
    --cc=dwalsh@redhat.com \
    --cc=jbrindle@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.