Skip to content
Snippets Groups Projects
Select Git revision
  • ee28857df184a8f2b5c35a6f93a1f755d679c051
  • master default protected
  • android-7.1.2_r28_klist
  • pie-cts-release
  • pie-vts-release
  • pie-cts-dev
  • oreo-mr1-iot-release
  • sdk-release
  • oreo-m6-s4-release
  • oreo-m4-s12-release
  • pie-release
  • pie-r2-release
  • pie-r2-s1-release
  • oreo-vts-release
  • oreo-cts-release
  • oreo-dev
  • oreo-mr1-dev
  • pie-gsi
  • pie-platform-release
  • pie-dev
  • oreo-cts-dev
  • android-o-mr1-iot-release-1.0.4
  • android-9.0.0_r8
  • android-9.0.0_r7
  • android-9.0.0_r6
  • android-9.0.0_r5
  • android-8.1.0_r46
  • android-8.1.0_r45
  • android-n-iot-release-smart-display-r2
  • android-vts-8.1_r5
  • android-cts-8.1_r8
  • android-cts-8.0_r12
  • android-cts-7.1_r20
  • android-cts-7.0_r24
  • android-o-mr1-iot-release-1.0.3
  • android-cts-9.0_r1
  • android-8.1.0_r43
  • android-8.1.0_r42
  • android-n-iot-release-smart-display
  • android-p-preview-5
  • android-9.0.0_r3
41 results

mls

  • Jeff Vander Stoep's avatar
    6231b4d9
    Enforce per-app data protections for targetSdk 28+ · 6231b4d9
    Jeff Vander Stoep authored
    Adds per-app categories to untrusted app domains and their
    app data types. Per-app categories are in addition to the
    existing per-user categories.
    
    Apps targeting sdk version 28+ will now have the following
    characteristics:
    Domain: u:r:untrusted_app:s0:c[0-9]+,c[0-9]+,c[0-9],c[0-9]
    Data context: u:object_r:app_data_file:s0:c[0-9]+,c[0-9]+,c[0-9],c[0-9]
    
    Whereas apps targeting 27- will look like:
    Domain: u:r:untrusted_app_27:s0:c[0-9]+,c[0-9]+
    Data context: u:object_r:app_data_file:s0:c[0-9]+,c[0-9]+
    
    To ensure backwards compatibility with previous SDK versions,
    the levelFrom=all now enforces categories by dominance instead of
    equality. Apps with per-app and per-user categories will continue
    to have selinux permissions (but not necessarily unix permissions)
    to access app data with only per-user categories, but apps with only
    per-user categories will not be able to access the data of apps with
    both per-app and per-user categories.
    
    Bug: 63897054
    Test: Boot sailfish, run apps, verify no new selinux denials.
    Test: cts-tradefed run cts -m CtsSelinuxTargetSdkCurrentTestCases
    Test: cts-tradefed run cts -m CtsSelinuxTargetSdk27TestCases
    Test: cts-tradefed run cts -m CtsSelinuxTargetSdk25TestCases
    Test: adb sideload an OTA and verify that files are correctly labeled.
    Change-Id: I64b013874fe87b55f47e817a1279e76ecf86b7c0
    6231b4d9
    History
    Enforce per-app data protections for targetSdk 28+
    Jeff Vander Stoep authored
    Adds per-app categories to untrusted app domains and their
    app data types. Per-app categories are in addition to the
    existing per-user categories.
    
    Apps targeting sdk version 28+ will now have the following
    characteristics:
    Domain: u:r:untrusted_app:s0:c[0-9]+,c[0-9]+,c[0-9],c[0-9]
    Data context: u:object_r:app_data_file:s0:c[0-9]+,c[0-9]+,c[0-9],c[0-9]
    
    Whereas apps targeting 27- will look like:
    Domain: u:r:untrusted_app_27:s0:c[0-9]+,c[0-9]+
    Data context: u:object_r:app_data_file:s0:c[0-9]+,c[0-9]+
    
    To ensure backwards compatibility with previous SDK versions,
    the levelFrom=all now enforces categories by dominance instead of
    equality. Apps with per-app and per-user categories will continue
    to have selinux permissions (but not necessarily unix permissions)
    to access app data with only per-user categories, but apps with only
    per-user categories will not be able to access the data of apps with
    both per-app and per-user categories.
    
    Bug: 63897054
    Test: Boot sailfish, run apps, verify no new selinux denials.
    Test: cts-tradefed run cts -m CtsSelinuxTargetSdkCurrentTestCases
    Test: cts-tradefed run cts -m CtsSelinuxTargetSdk27TestCases
    Test: cts-tradefed run cts -m CtsSelinuxTargetSdk25TestCases
    Test: adb sideload an OTA and verify that files are correctly labeled.
    Change-Id: I64b013874fe87b55f47e817a1279e76ecf86b7c0