We aren't actively developing those branches any more (beyond
periodically merging latest master whenever we do that for seandroid).
Ditto for revoke-perms. We lack an equivalent to the small set of clear,
well-defined goals that we had for the kernel MAC policy for the
middleware, and it seems difficult to define such a set of goals that
improves security yet doesn't break compatibility. Both mechanisms
ultimately require a policy that can distinguish third party apps in
order to be useful; a move that Google has frowned upon in the past. And
Google seems less interested in any changes to the middleware security
model other than possibly opt-in models. We've instead moved to more
targeted improvements in the middleware area that don't involve per app
policy in any way.
On 06/28/2013 11:52 AM, Richard Haines wrote:
I know its all experimental but are there any plans regarding CP_MAC and
Intent_MAC about how they will be developed and whether they will be seen in
Android AOSP releases.
Thanks again
Richard
--
This message was distributed to subscribers of the seandroid-list mailing list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe seandroid-list" without quotes as the message.
