Reduce the number of processes that can start adbd
This change makes it such that only init can start adbd directly. It also introduces new rules for ctl.{start,stop,restart} properties such that only usbd and recovery (and su, since it's permissive) can directly ask init to start adbd. Bug: 64720460 Test: adbd still runs Test: /data/nativetest64/adbd_test/adbd_test Test: python system/core/adb/test_adb.py Test: "USB debugging" in System Settings still start/stop adbd Test: Recovery menu still make the device show as "recovery" in adb devices Test: "Apply update from ADB" in recovery menu still works Change-Id: Iafcda8aa44e85129afcc958036b472d856fa1192
Showing
- private/compat/26.0/26.0.cil 1 addition, 1 deletionprivate/compat/26.0/26.0.cil
- private/compat/27.0/27.0.cil 1 addition, 1 deletionprivate/compat/27.0/27.0.cil
- private/property_contexts 5 additions, 0 deletionsprivate/property_contexts
- public/adbd.te 4 additions, 0 deletionspublic/adbd.te
- public/property.te 2 additions, 0 deletionspublic/property.te
- public/recovery.te 1 addition, 1 deletionpublic/recovery.te
- public/usbd.te 2 additions, 0 deletionspublic/usbd.te
Loading
Please register or sign in to comment