Well if by mainstreamed you mean the code is in Google's AOSP tree, then we pretty much are mainstreamed. However, currently no Google Android device has shipped with SEAndroid as it has never been enabled in the Kernel. With that said, all the conditional compilation options have been removed for the support, the only thing preventing it is the Kernel.
On Mon, Apr 8, 2013 at 12:57 PM, James Puderer <[email protected]>wrote: > I'm just getting started with SE Android. So far, I really like the > approach. You guys have done some really great work! > > I'm very curious to know if there has been any indication from Google as > to if, when, and how SE Android might be mainstreamed into AOSP? > > I'm also wondering if the goal of mainstreaming SE Android is to define a > "blessed" base policy that gets enforced by default on all Android devices, > or if it is expected that this would largely remain up to the device OEMs > (so long as the devices pass CTS). > > Thanks, > James > -- Respectfully, William C Roberts
