On Wed, Jun 17, 2015 at 5:49 AM, Stephen Smalley <[email protected]> wrote:

> On 06/16/2015 12:04 PM, Nick Kralevich wrote:
> >
> >
> > On Tue, Jun 16, 2015 at 8:28 AM, Stephen Smalley <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> >     On 06/16/2015 11:27 AM, Jeffrey Vander Stoep wrote:
> >     >> Shouldn't they use the final/upstream version instead, i.e.
> >     >> https://android-review.googlesource.com/#/c/152510/
> >     >>
> >     >
> >     > It looks like Android M will remain on the previous version of the
> >     > patches. Future versions will move to the final version that
> Stephen
> >     > linked to. I plan on merging the final version into AOSP master
> once M
> >     > is forked.
> >
> >     That's a bit troubling; it means that M will ship with a forked
> >     policy.30 format that can't be handled by any upstream SELinux
> tools...
> >
> >
> > It's unfortunate but the reality. It will be fixed in a future Android
> > release.
> >
> > At this point, only SELinux tools distributed in AOSP are supported on
> > Android. SELinux tools distributed from other places may or may not work.
>
> That increases the importance of getting a subset of setools (e.g.
> sesearch, sediff) into AOSP or re-implementing the relevant
> functionality as part of sepolicy-analyze.
>
>
Off topic the bundled audit2allow on master that gets added to PATH doesn't
run on my machine:
$ audit2allow
/home/bill/workspace/aosp/external/selinux/prebuilts/bin/audit2allow: 4:
/home/bill/workspace/aosp/external/selinux/prebuilts/bin/audit2allow: [[:
not found
audit2allow is only supported on linux

printing unamestr results in linux



> _______________________________________________
> Seandroid-list mailing list
> [email protected]
> To unsubscribe, send email to [email protected].
> To get help, send an email containing "help" to
> [email protected].
>



-- 
Respectfully,

William C Roberts
_______________________________________________
Seandroid-list mailing list
[email protected]
To unsubscribe, send email to [email protected].
To get help, send an email containing "help" to 
[email protected].

Reply via email to