From: Joshua Brindle <jbrindle@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: <selinux@tycho.nsa.gov>
Subject: Re: [RFC] Add initial clipboard access control implementation
Date: Fri, 14 Sep 2012 12:46:48 -0400 [thread overview]
Message-ID: <50535F78.3070003@tresys.com> (raw)
In-Reply-To: <1347640545.11029.63.camel@moss-pluto.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Fri, 2012-09-14 at 11:24 -0400, Joshua Brindle wrote:
>> This is an RFC for clipboard access controls in Android. I still need to do non-SELinux system guards and check for permission when onPrimaryClipChanged() sends notifications to apps listening for clipboard updates.
>>
>> Change-Id: Ib0b6aeca59511ce71832aee1afd4150d1514a63c
>> ---
>> .../java/com/android/server/ClipboardService.java | 25 ++++++++++++++++++++
>> 1 file changed, 25 insertions(+)
>
> Do you have a functioning policy for these controls (i.e. one that
> allows normal operation but prevents something bad from happening)?
>
Sort of. My policy is pretty hacked up because the only way this is
useful is if you have multiple, separate app domains, which the
appdomain attribute does a good job of not easily allowing without
duplicating all the rules.
To make devices behave as normal we just need:
allow appdomain appdomain : x_application_data paste;
in app.te, but that won't prevent pasting ever, someone who wants to use
this will have to make a new domain that isn't in the appdomain
attribute and copy all the rules.
On my todo list is to move all the appdomain rules to an interface so
that I can create new domains without access to each other but that
hasn't happened yet.
--
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:[~2012-09-14 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 15:24 [RFC] Add initial clipboard access control implementation Joshua Brindle
2012-09-14 16:35 ` Stephen Smalley
2012-09-14 16:46 ` Joshua Brindle [this message]
2012-09-14 17:51 ` Stephen Smalley
2012-09-14 18:07 ` Joshua Brindle
2012-09-14 18:49 ` 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=50535F78.3070003@tresys.com \
--to=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.