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

property_contexts

  • Stephen Smalley's avatar
    3235f61a
    Restrict /data/security and setprop selinux.reload_policy access. · 3235f61a
    Stephen Smalley authored
    
    Remove /data/security and setprop selinux.reload_policy access
    from unconfineddomain, and only add back what is needed to
    init (system_server already gets the required allow rules via
    the selinux_manage_policy macro).
    
    init (via init.rc post-fs-data) originally creates /data/security
    and may later restorecon it.  init also sets the property (also from
    init.rc post-fs-data) to trigger a reload once /data is mounted.
    The system_server (SELinuxPolicyInstallReceiver in particular) creates
    subdirectories under /data/security for updates, writes files to these
    subdirectories, creates the /data/security/current symlink to the update
    directory, and sets the property to trigger a reload when an update bundle
    is received.
    
    Add neverallow rules to ensure that we do not allow undesired access
    to security_file or security_prop.
    
    This is only truly meaningful if the support for /data/security policies
    is restored, but is harmless otherwise.
    
    Also drop the persist.mmac property_contexts entry; it was never used in
    AOSP, only in our tree (for middleware MAC) and is obsolete.
    
    Change-Id: I5ad5e3b6fc7abaafd314d31723f37b708d8fcf89
    Signed-off-by: default avatarStephen Smalley <sds@tycho.nsa.gov>
    3235f61a
    History
    Restrict /data/security and setprop selinux.reload_policy access.
    Stephen Smalley authored
    
    Remove /data/security and setprop selinux.reload_policy access
    from unconfineddomain, and only add back what is needed to
    init (system_server already gets the required allow rules via
    the selinux_manage_policy macro).
    
    init (via init.rc post-fs-data) originally creates /data/security
    and may later restorecon it.  init also sets the property (also from
    init.rc post-fs-data) to trigger a reload once /data is mounted.
    The system_server (SELinuxPolicyInstallReceiver in particular) creates
    subdirectories under /data/security for updates, writes files to these
    subdirectories, creates the /data/security/current symlink to the update
    directory, and sets the property to trigger a reload when an update bundle
    is received.
    
    Add neverallow rules to ensure that we do not allow undesired access
    to security_file or security_prop.
    
    This is only truly meaningful if the support for /data/security policies
    is restored, but is harmless otherwise.
    
    Also drop the persist.mmac property_contexts entry; it was never used in
    AOSP, only in our tree (for middleware MAC) and is obsolete.
    
    Change-Id: I5ad5e3b6fc7abaafd314d31723f37b708d8fcf89
    Signed-off-by: default avatarStephen Smalley <sds@tycho.nsa.gov>