Skip to content
Snippets Groups Projects
Select Git revision
  • android-7.1.2_r28_klist
  • master default protected
  • 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
40 results

Android.mk

Blame
    • Alex Klyubin's avatar
      5596172d
      Device-agnostic policy for vendor image · 5596172d
      Alex Klyubin authored
      Default HAL implementations are built from the platform tree and get
      placed into the vendor image. The SELinux rules needed for these HAL
      implementations to operate thus need to reside on the vendor
      partition.
      
      Up to now, the only place to define such rules in the source tree was
      the system/sepolicy/public directory. These rules are placed into the
      vendor partition. Unfortunately, they are also placed into the
      system/root partition, which thus unnecessarily grants these rules to
      all HAL implementations of the specified service, default/in-process
      shims or not.
      
      This commit adds a new directory, system/sepolicy/vendor, whose
      rules are concatenated with the device-specific rules at build time.
      These rules are thus placed into the vendor partition and are not
      placed into the system/root partition.
      
      Test: No change to SELinux policy.
      Test: Rules placed into vendor directory end up in nonplat* artefacts,
            but not in plat* artefacts.
      Bug: 34715716
      Change-Id: Iab14aa7a3311ed6d53afff673e5d112428941f1c
      5596172d
      History
      Device-agnostic policy for vendor image
      Alex Klyubin authored
      Default HAL implementations are built from the platform tree and get
      placed into the vendor image. The SELinux rules needed for these HAL
      implementations to operate thus need to reside on the vendor
      partition.
      
      Up to now, the only place to define such rules in the source tree was
      the system/sepolicy/public directory. These rules are placed into the
      vendor partition. Unfortunately, they are also placed into the
      system/root partition, which thus unnecessarily grants these rules to
      all HAL implementations of the specified service, default/in-process
      shims or not.
      
      This commit adds a new directory, system/sepolicy/vendor, whose
      rules are concatenated with the device-specific rules at build time.
      These rules are thus placed into the vendor partition and are not
      placed into the system/root partition.
      
      Test: No change to SELinux policy.
      Test: Rules placed into vendor directory end up in nonplat* artefacts,
            but not in plat* artefacts.
      Bug: 34715716
      Change-Id: Iab14aa7a3311ed6d53afff673e5d112428941f1c