Hello all, I just started looking at SEAndroid and have a question about SEAndroid policies. How are the policies made? I see that lots of changes are being made to the policies ( https://android-review.googlesource.com/#/q/project:platform/external/sepolicy) but how are these policies being made? What is the intuition behind these changes? Do you run any static analysis to see which processes needs to be allowed communicate?
Also, I read the paper "Security Enhanced Android: Bringing Flexible MAC to Android" and it states that the policies are made from scratch. Does it mean SEAndroid used none of the SELinux policies? I suspect since Android is built on the linux kernel so there must be some policies that comes from SELinux policies. Thanks, Daniel
_______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
