On 11/24/2014 01:29 PM, William Roberts wrote: > Is this a condition of it being policy version 23? Are you uploading this > to AOSP, and perhaps we could > print a warning if policy vers < 26. The tool should either work or fail on > this condition not segfault. > > This patch seems to be for libsepol, is that correct?
Yes, it is a bug in libsepol for policy versions less than 24. I also posted the patch to selinux list so it will be fixed in a future upstream libsepol version. I could upload it to AOSP but it is somewhat moot there since we would never use a policy version less than 26 now (given dependence on name-based transitions in sepolicy) and even when we first started, we were using policy version 24 since it was supported even by the old 2.6.29 emulator kernels. You would only need a policy version < 24 for kernels older than 2.6.27, which I can't imagine anyone doing for any current or new devices. At some point I intend to upload a new upstream release of libsepol and checkpolicy to AOSP, at which point it would pick up any of these fixes. _______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
