From: Greg KH <gregkh@linuxfoundation.org>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: linux-kernel@vger.kernel.org, arve@android.com, nnk@google.com,
paul@paul-moore.com, selinux@tycho.nsa.gov,
linux-security-module@vger.kernel.org, jmorris@namei.org
Subject: Re: [PATCH] Add security hooks to binder and implement the hooks for SELinux.
Date: Thu, 22 Jan 2015 16:51:50 +0800 [thread overview]
Message-ID: <20150122085150.GB1268@kroah.com> (raw)
In-Reply-To: <1421855650-22522-1-git-send-email-sds@tycho.nsa.gov>
On Wed, Jan 21, 2015 at 10:54:10AM -0500, Stephen Smalley wrote:
> Add security hooks to the binder and implement the hooks for SELinux.
> The security hooks enable security modules such as SELinux to implement
> controls over binder IPC. The security hooks include support for
> controlling what process can become the binder context manager
> (binder_set_context_mgr), controlling the ability of a process
> to invoke a binder transaction/IPC to another process (binder_transaction),
> controlling the ability of a process to transfer a binder reference to
> another process (binder_transfer_binder), and controlling the ability
> of a process to transfer an open file to another process (binder_transfer_file).
>
> These hooks have been included in the Android kernel trees since Android 4.3.
Very interesting, I missed the fact that these were added in that tree,
thanks for digging it out and submitting it.
I'd like some acks from some Android developers before I take these.
Or, if it's easier for them to go through the security tree, that's fine
with me as well.
thanks,
greg k-h
next prev parent reply other threads:[~2015-01-22 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 15:54 [PATCH] Add security hooks to binder and implement the hooks for SELinux Stephen Smalley
2015-01-22 8:51 ` Greg KH [this message]
2015-01-22 17:37 ` Jeffrey Vander Stoep
2015-01-22 17:48 ` Nick Kralevich
2015-01-22 18:09 ` Casey Schaufler
2015-01-22 18:47 ` Stephen Smalley
2015-01-23 2:30 ` Greg KH
2015-01-23 21:56 ` Casey Schaufler
2015-01-23 23:45 ` Greg KH
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=20150122085150.GB1268@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nnk@google.com \
--cc=paul@paul-moore.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox