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

system_server.te

  • Nick Kralevich's avatar
    2234f9ff
    gatekeeperd: neverallow non-system_server binder call · 2234f9ff
    Nick Kralevich authored
    The current neverallow rule (compile time assertion)
    
      neverallow { domain -gatekeeperd -system_server } gatekeeper_service:service_manager find;
    
    asserts that no rule is present which allows processes other than
    system_server from asking servicemanager for a gatekeeperd token.
    
    However, if system_server leaks the token to other processes, it may
    be possible for those processes to access gatekeeperd directly, bypassing
    servicemanager.
    
    Add a neverallow rule to assert that no process other than system_server
    are allowed to make binder calls to gatekeeperd. Even if another process
    was to manage to get a binder token to gatekeeperd, it would be useless.
    
    Remove binder_service() from gatekeeperd. The original use of the
    binder_service() macro was to widely publish a binder service.
    If this macro is present and the calling process has a gatekeeperd
    binder token, it's implicitly possible for the following processes
    to make a binder call to gatekeeperd:
    
     * all app processes
     * dumpstate
     * system_server
     * mediaserver
     * surfaceflinger
    
    Removing binder_service revokes this implicit access.
    
    Add explicit access for system_server to make binder calls to
    gatekeeperd.
    
    Add explicit access for gatekeeperd to make calls to keystore.
    This was implicitly granted via binder_service() before, but now
    needs to be explicit.
    
    Change-Id: I23c1573d04ab670a42660d5922b39eecf4265b66
    2234f9ff
    History
    gatekeeperd: neverallow non-system_server binder call
    Nick Kralevich authored
    The current neverallow rule (compile time assertion)
    
      neverallow { domain -gatekeeperd -system_server } gatekeeper_service:service_manager find;
    
    asserts that no rule is present which allows processes other than
    system_server from asking servicemanager for a gatekeeperd token.
    
    However, if system_server leaks the token to other processes, it may
    be possible for those processes to access gatekeeperd directly, bypassing
    servicemanager.
    
    Add a neverallow rule to assert that no process other than system_server
    are allowed to make binder calls to gatekeeperd. Even if another process
    was to manage to get a binder token to gatekeeperd, it would be useless.
    
    Remove binder_service() from gatekeeperd. The original use of the
    binder_service() macro was to widely publish a binder service.
    If this macro is present and the calling process has a gatekeeperd
    binder token, it's implicitly possible for the following processes
    to make a binder call to gatekeeperd:
    
     * all app processes
     * dumpstate
     * system_server
     * mediaserver
     * surfaceflinger
    
    Removing binder_service revokes this implicit access.
    
    Add explicit access for system_server to make binder calls to
    gatekeeperd.
    
    Add explicit access for gatekeeperd to make calls to keystore.
    This was implicitly granted via binder_service() before, but now
    needs to be explicit.
    
    Change-Id: I23c1573d04ab670a42660d5922b39eecf4265b66