android_vendor_lineage

Commit Graph

Author	SHA1	Message	Date
d34d	79eda9ebb8	sepolicy: Put theme service in its own context Allow the theme manager and its data to be sandboxed in its own context Change-Id: I7898663d1c196bfe04fa4c539d20191a43fde284	8 years ago
dhacker29	c552843f1a	sepolicy: Allow CMUpdater/uncrypt access to recovery_cache_file Change-Id: I514d128160ed4e04564077d7a2e2ad297af92e28	10 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

Author

SHA1

Message

Date

d34d

79eda9ebb8

sepolicy: Put theme service in its own context

Allow the theme manager and its data to be sandboxed in
its own context

Change-Id: I7898663d1c196bfe04fa4c539d20191a43fde284

dhacker29

c552843f1a

sepolicy: Allow CMUpdater/uncrypt access to recovery_cache_file

Change-Id: I514d128160ed4e04564077d7a2e2ad297af92e28

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

3 Commits (a434e63395933d22ef8731858ee9af8e824408d3)