All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <brindle@quarksecurity.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	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 15:42:59 -0400	[thread overview]
Message-ID: <52716143.3080609@quarksecurity.com> (raw)
In-Reply-To: <52715E75.5000005@redhat.com>

Daniel J Walsh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> We are trying to shrink out cloud image as small as possible.  One idea was to
> shrink SELinux Policy footprint by adding compression to it.
>
> Here is a patch I have been fooling around with which would read a policy.29
> file if it was compressed with xz.
>
> xz compression does around a 90% compression on the policy file,  and does not
> slow the load in any meaningfull way.
>
> I also have done a patch to try out gzip.
>
> gzip and xz are already used in systemd, which means we would not need to add
> a new requirement to the minimal system.
>
> xz seems quicker and smaller then gzip.
>
> Have not started playing with libsemanage yet.
>
> What do you think?  Is xz availabel on Android?

No.

Is there a reason you wouldn't just have systemd decompress it before 
loading it? I guess if you want all the existing tools/libraries to work 
without any changes it would need to be build in to libselinux rather 
done outside of the library.

Android's libselinux is forked anyway so this probably wouldn't flow to 
Android.

--
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 19: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 [this message]
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
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=52716143.3080609@quarksecurity.com \
    --to=brindle@quarksecurity.com \
    --cc=dwalsh@redhat.com \
    --cc=jbrindle@tresys.com \
    --cc=sds@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.