Skip to content
Snippets Groups Projects
  1. Feb 06, 2017
  2. Feb 03, 2017
  3. Feb 02, 2017
  4. Feb 01, 2017
  5. Jan 31, 2017
    • Calin Juravle's avatar
      Remove SElinux audit to libart_file · 01ee59a7
      Calin Juravle authored
      Since it was introduced it caused quite a few issues and it spams the
      SElinux logs unnecessary.
      
      The end goal of the audit was to whitelist the access to the
      interpreter. However that's unfeasible for now given the complexity.
      
      Test: devices boots and everything works as expected
            no more auditallow logs
      
      Bug: 29795519
      Bug: 32871170
      Change-Id: I9a7a65835e1e1d3f81be635bed2a3acf75a264f6
      01ee59a7
    • Alex Klyubin's avatar
      Merge "Device-agnostic policy for vendor image" · e9f4b599
      Alex Klyubin authored
      am: 9e90f83e
      
      Change-Id: Idf1178328847bf597005c66c7652e4bda25c3bdd
      e9f4b599
    • Alex Klyubin's avatar
      9e90f83e
    • Mark Salyzyn's avatar
      logd: restrict access to /dev/event-log-tags · 650c101f
      Mark Salyzyn authored
      am: d33a9a19
      
      Change-Id: I8f95628067641e773623603681f226dab4939f2a
      650c101f
    • Mark Salyzyn's avatar
      logd: add getEventTag command and service · 384ce662
      Mark Salyzyn authored
      The event log tag service uses /dev/event-log-tags, pstore and
      /data/misc/logd/event-log-tags as sticky storage for the invented
      log tags.
      
      Test: gTest liblog-unit-tests, logd-unit-tests & logcat-unit-tests
      Bug: 31456426
      Change-Id: Iacc8f36f4a716d4da8dca78a4a54600ad2a288dd
      384ce662
    • Mark Salyzyn's avatar
      logd: restrict access to /dev/event-log-tags · d33a9a19
      Mark Salyzyn authored
      Create an event_log_tags_file label and use it for
      /dev/event-log-tags.  Only trusted system log readers are allowed
      direct read access to this file, no write access.  Untrusted domain
      requests lack direct access, and are thus checked for credentials via
      the "plan b" long path socket to the event log tag service.
      
      Test: gTest logd-unit-tests, liblog-unit-tests and logcat-unit-tests
      Bug: 31456426
      Bug: 30566487
      Change-Id: Ib9b71ca225d4436d764c9bc340ff7b1c9c252a9e
      d33a9a19
    • Alex Klyubin's avatar
      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
    • Tao Bao's avatar
      Merge "recovery: Allow accessing sysfs_leds." · 964c783f
      Tao Bao authored
      am: 04641948
      
      Change-Id: I8e2a131d51725e4ba2cb5867fe99565f810e6381
      964c783f
    • Yin-Chia Yeh's avatar
      Merge "Camera: grant system file perm for Treble" · c701272d
      Yin-Chia Yeh authored
      am: 81a73508
      
      Change-Id: I1fd4a6c21ae80463fe67cc85db2949382453b948
      c701272d
    • Treehugger Robot's avatar
      04641948
    • Treehugger Robot's avatar
      81a73508
  6. Jan 30, 2017
  7. Jan 29, 2017
  8. Jan 28, 2017
  9. Jan 27, 2017
    • Janis Danisevskis's avatar
      Preliminary policy for hal_keymaster (TREBLE) · e8acd769
      Janis Danisevskis authored
      This adds the premissions required for
      android.hardware.keymaster@2.0-service to access the keymaster TA
      as well as for keystore and vold to lookup and use
      android.hardware.keymaster@2.0-service.
      
      IT DOES NOT remove the privileges from keystore and vold to access
      the keymaster TA directly.
      
      Test: Run keystore CTS tests
      Bug: 32020919
      
      (cherry picked from commit 5090d6f3)
      
      Change-Id: Ib02682da26e2dbcabd81bc23169f9bd0e832eb19
      e8acd769
Loading