106 Commits (8b0f16fc3ff213fbdeba865ef942ef4df761b785)

Author	SHA1	Message	Date
Ricardo Cerqueira	98c81ead7a	selinux: Fix asec mounting ... Change-Id: I92392f3d810dfaf8dfc35f5c9170178a651d28dc	11 years ago
dhacker29	26a925919b	sepolicy: f2fs: Allow fs_use_xattr ... Change-Id: I458d464598777fa06751dad0aa9cfd4d903a4de1	11 years ago
Ricardo Cerqueira	e58e23e131	selinux: Add missing seapp_contexts file ... Change-Id: I6bda9e4876b9053ea16fe3c11c21b9c1e7acb17a	11 years ago
Ricardo Cerqueira	ac8d09538e	selinux: Add CM-specific file_contexts ... Change-Id: Ie70c59acedbb7be2f5b34a83c1d3d011f440ba05	11 years ago
Ricardo Cerqueira	8521d46944	selinux: CM policies are now inserted last ... Inclusion of the makefile is done by the build system to enforce the wanted order Change-Id: I86d7c6fb08b6bb1f6e0385e951a54827345aaf84	11 years ago
William Roberts	9642d1dd8b	sepolicy: Start CM Common sepolicy ... Rather than having to maintain out of tree changes, it is often easier to maintain a hiearchy of changes, starting with the vendors common config file. From there, inheriting products can pick up a base and start to add or remove certain bits from it, making use of the BOARD_SEPOLICY_* functions documented in external/sepolicy/README. Change-Id: I28a4aaf6c126535f0a88001582641b234a750015	11 years ago