From: Stephen Smalley <sds@tycho.nsa.gov>
To: Bhargava Shastry <bshas3@gmail.com>
Cc: SELinux@tycho.nsa.gov
Subject: Re: SELinux on Android
Date: Fri, 04 Nov 2011 12:59:58 -0400 [thread overview]
Message-ID: <1320425998.1015.31.camel@moss-pluto> (raw)
In-Reply-To: <CAGGozWR6yGyQaxgSED+NdAyLYGzkjDhdWmMxnB=B0qEBAEOtLA@mail.gmail.com>
On Fri, 2011-11-04 at 17:25 +0100, Bhargava Shastry wrote:
> Dear Mr. Smalley,
>
> Thanks for your inputs. I did go through the slides of your recent
> presentation on a case for SELinux enhanced Android phone. You have
> done a great job re-engineering Android to retrofit SELinux.
>
> I was wondering how much effort it is to actually port a subset of
> SELinux's userspace (e.g., loadpolicy, chcon and a few others) tools
> to Android? Does it entail major changes to Android's existing
> toolchain including modifications to its bionic libc? Also, I was
> wondering if you also undertook a port of coreutils as well (to enable
> the -Z option for utils like ps and ls)?
I did need to make some changes to bionic, e.g. adding the xattr system
calls to SYSCALLS.TXT and re-generating the syscall wrapper functions
via gensyscalls.py, adding support for the AT_SECURE auxv flag. Then I
could port a subset of libselinux. To support the SELinux commands and
-Z option, I modified the Android toolbox with support for ps -Z and ls
-Z and added new commands to it for various SELinux tools. To date, I
have added chcon, [gs]etenforce, [gs]etsebool, load_policy, restorecon,
and runcon.
--
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.
next prev parent reply other threads:[~2011-11-04 16:59 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 [this message]
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
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=1320425998.1015.31.camel@moss-pluto \
--to=sds@tycho.nsa.gov \
--cc=SELinux@tycho.nsa.gov \
--cc=bshas3@gmail.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.