All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Bhargava Shastry <bshas3@gmail.com>
Cc: Eric Paris <eparis@parisplace.org>,
	SELinux@tycho.nsa.gov, James Morris <jmorris@namei.org>
Subject: Re: SELinux on Android
Date: Mon, 21 Nov 2011 13:32:53 -0500	[thread overview]
Message-ID: <1321900374.9385.39.camel@moss-pluto> (raw)
In-Reply-To: <CAGGozWQXo5bXgVKa0t3pO+45Vj70LJA12dF2ovX6Hm9KnYNNQQ@mail.gmail.com>

On Mon, 2011-11-21 at 19:18 +0100, Bhargava Shastry wrote:
>         You need to add a fs_use_xattr statement to your policy
>         configuration
>         for yaffs2.  Similar to the existing statements for ext[234].
> 
> Thanks. I have the sources for a reference SELinux policy from the
> tresys website. Unfortunately, with default policy build options, the
> resulting monolithic policy is huge. I am using an Ubuntu machine; any
> hints as to where to start for a minimal policy for Android. I tried
> selectively building only basic modules but there are intricate
> dependencies (checkpolicy throws up unresolved symbols error) between
> modules that is hard to disentangle. 

It doesn't make much sense to use the reference policy for Android,
because the Android userspace is completely different from a typical
Linux distribution.  I created a policy from scratch for my work.

You can generate a minimal policy from the kernel tree (see
scripts/selinux/mdp).  However, that generated policy will only take you
so far since it lacks any of the macro definitions/build infrastructure
and since it places everything in a single type/domain.  So you can
start there, but you'll likely want to split it out into multiple files,
add some of the macros from refpolicy or the original example policy,
and start defining individual domains and types.

-- 
Stephen Smalley
National Security Agency


--
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:[~2011-11-21 18:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04 10:16 SELinux on Android Bhargava Shastry
2011-11-04 10:54 ` Russell Coker
2011-11-04 12:32 ` Stephen Smalley
2011-11-04 16:25   ` Bhargava Shastry
2011-11-04 16:59     ` Stephen Smalley
2011-11-10 10:33       ` Bhargava Shastry
2011-11-10 12:48         ` Russell Coker
2011-11-10 13:11           ` Eric Paris
2011-11-10 13:12         ` Stephen Smalley
2011-11-10 13:26           ` Bhargava Shastry
2011-11-10 16:26             ` Stephen Smalley
2011-11-11 11:33               ` Bhargava Shastry
2011-11-16 18:15                 ` Bhargava Shastry
2011-11-16 18:35                   ` Eric Paris
2011-11-17 10:15                     ` Bhargava Shastry
2011-11-17 13:39                       ` Stephen Smalley
2011-11-21 15:45                         ` Bhargava Shastry
2011-11-21 15:51                           ` Stephen Smalley
2011-11-21 18:18                             ` Bhargava Shastry
2011-11-21 18:32                               ` Stephen Smalley [this message]
2011-11-22 19:25                                 ` Bhargava Shastry
2011-11-22 19:29                                   ` Stephen Smalley
2011-11-22 22:03                                   ` Russell Coker
2011-12-01 18:42                                     ` Bhargava Shastry
2011-12-01 19:04                                       ` Stephen Smalley
2011-12-02 10:37                                         ` Bhargava Shastry
2011-11-17 13:37                   ` Stephen Smalley

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=1321900374.9385.39.camel@moss-pluto \
    --to=sds@tycho.nsa.gov \
    --cc=SELinux@tycho.nsa.gov \
    --cc=bshas3@gmail.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    /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.