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
    • Nick Kralevich's avatar
      c3c9052b
      Make DEFAULT_SYSTEM_DEV_CERTIFICATE available in keys.conf · c3c9052b
      Nick Kralevich authored
      In 9af6f1bd, the -d option
      was dropped from insertkeys.py. This was done to allow an
      Android distribution to replace the default version of
      keys.conf distributed in external/sepolicy/keys.conf. keys.conf
      was modified to reference the publicly known test keys in
      build/target/product/security.
      
      Unfortunately, this broke Google's build of Android. Instead
      of incorporating our keys directory, we were using the
      default AOSP keys. As a result, apps were getting assigned
      to the wrong SELinux domain. (see "Steps to reproduce" below)
      
      This change continues to allow others to replace keys.conf,
      but makes DEFAULT_SYSTEM_DEV_CERTIFICATE available as an
      environment variable in case the customized version wants to
      make reference to it. This change also modifies the stock
      version of keys.conf to use DEFAULT_SYSTEM_DEV_CERTIFICATE,
      which should be appropriate for most Android distributions.
      It doesn't make any sense to force each OEM to have a copy of
      this file.
      
      Steps to reproduce.
      
      1) Compile and boot Android.
      2) Run the following command: "adb shell ps -Z | grep process.media"
      
      Expected:
      
        $ adb shell ps -Z | grep process.media
        u:r:media_app:s0               u0_a5     1332  202   android.process.media
      
      Actual:
      
        $ adb shell ps -Z | grep process.media
        u:r:untrusted_app:s0           u0_a5     3617  187   android.process.media
      
      Bug: 11327304
      Change-Id: Ica24fb25c5f9c0e2f4d181718c757cf372467822
      c3c9052b
      History
      Make DEFAULT_SYSTEM_DEV_CERTIFICATE available in keys.conf
      Nick Kralevich authored
      In 9af6f1bd, the -d option
      was dropped from insertkeys.py. This was done to allow an
      Android distribution to replace the default version of
      keys.conf distributed in external/sepolicy/keys.conf. keys.conf
      was modified to reference the publicly known test keys in
      build/target/product/security.
      
      Unfortunately, this broke Google's build of Android. Instead
      of incorporating our keys directory, we were using the
      default AOSP keys. As a result, apps were getting assigned
      to the wrong SELinux domain. (see "Steps to reproduce" below)
      
      This change continues to allow others to replace keys.conf,
      but makes DEFAULT_SYSTEM_DEV_CERTIFICATE available as an
      environment variable in case the customized version wants to
      make reference to it. This change also modifies the stock
      version of keys.conf to use DEFAULT_SYSTEM_DEV_CERTIFICATE,
      which should be appropriate for most Android distributions.
      It doesn't make any sense to force each OEM to have a copy of
      this file.
      
      Steps to reproduce.
      
      1) Compile and boot Android.
      2) Run the following command: "adb shell ps -Z | grep process.media"
      
      Expected:
      
        $ adb shell ps -Z | grep process.media
        u:r:media_app:s0               u0_a5     1332  202   android.process.media
      
      Actual:
      
        $ adb shell ps -Z | grep process.media
        u:r:untrusted_app:s0           u0_a5     3617  187   android.process.media
      
      Bug: 11327304
      Change-Id: Ica24fb25c5f9c0e2f4d181718c757cf372467822