| 928cf933aadcd209afc851784c91bade44afdbe1 |
|
28-Dec-2016 |
Mark Salyzyn <salyzyn@google.com> |
logpersist: do not permit dynamic transition to domain
We allow domains to manually transition to logpersist for userdebug
or eng debug logging permissions that would be counter to monitoring
limits on a released user build.
Test: compile
Bug: 30566487
Change-Id: I03a81c75cbd2b44617e4b27c4c083a26a0e0fa87
/system/sepolicy/public/logpersist.te
|
| 5f25239c2cbf3e84b242a282094cf2784765701d |
|
21-Dec-2016 |
Mark Salyzyn <salyzyn@google.com> |
init: permit logpersist transition for the time being (STOPSHIP)
mmi-based products insists on running persistent logcat directly.
Test: build
Bug: 30566487
Change-Id: I6397f5faedb2a4a5e2f4cfc5387977ae9c54b2d4
/system/sepolicy/public/logpersist.te
|
| df125b90b456748f834df06e69d9e8aa05054c69 |
|
06-Dec-2016 |
Mark Salyzyn <salyzyn@google.com> |
init: only allowed to transition to logpersist or logd
Generate a compile time error if someone unexpectedly tries to
transition into logpersist or logd domain.
Test: compile
Bug: 30566487
Change-Id: Ib55f301f104ad63de5ac513cdc9dc9937e3ba48d
/system/sepolicy/public/logpersist.te
|
| da62cb4dda9c7e77dc67ced441d7ffe6fd3f2f2a |
|
10-Aug-2016 |
Mark Salyzyn <salyzyn@google.com> |
logcat: introduce split to logd and logpersist domains
- transition to logpersist from init
- sort some overlapping negative references
- intention is to allow logpersist to be used by vendor
userdebug logging
Test: gTest liblog-unit-tests, logd-unit-tests & logcat-unit-tests
Bug: 30566487
Change-Id: I7806f5a2548cbe0c1f257a0ba2855f2eb69d8e7c
/system/sepolicy/public/logpersist.te
|