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 10:51:37 -0500 [thread overview]
Message-ID: <1321890697.9385.20.camel@moss-pluto> (raw)
In-Reply-To: <CAGGozWT9PP-p4-UA6WJtiZmwHE1ot_Of85pKQRLGeab37e4kaQ@mail.gmail.com>
On Mon, 2011-11-21 at 16:45 +0100, Bhargava Shastry wrote:
> Hello,
>
> On loading an SELinux policy, I see that SELinux recognises the YAFFS
> blocks on Android as FS where labeling is not supported. Here is a
> sample dmesg print:
> "SELinux: initialized (dev mtdblock3, type yaffs2), not configured for
> labeling"
>
> On looking into the SELinux code, I see that such a print is spat out
> on a check for a file-system superblock security attribute called
> "behavior". Could I possibly correct this by changing something in the
> YAFFS file-system code. I tried mounting the yaffs partition by
> appening the context= option in Android's init.rc but the mount fails.
> I should add that I am able to execute getfilecon on YAFFS (extended
> attributes have been ported to YAFFS) successfully but setfilecon
> fails possibly due to the above debug print. And as previously
> mentioned, I attempt set/getfilecon only after a load_policy. Also,
> all other filesystems (rootfs, procfs, tmpfs etc. are correctly
> initialised on policy load)
You need to add a fs_use_xattr statement to your policy configuration
for yaffs2. Similar to the existing statements for ext[234].
--
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-21 15:51 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 [this message]
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=1321890697.9385.20.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.