OSDN Git Service

Fix a security exception when checking cross-profile caller-id cap.
authorAmith Yamasani <yamasani@google.com>
Tue, 22 Jul 2014 00:04:44 +0000 (17:04 -0700)
committerAmith Yamasani <yamasani@google.com>
Tue, 22 Jul 2014 00:04:44 +0000 (17:04 -0700)
No need to enforce that the caller is in the system process.
We're only checking if the device policy is allowing access.

Bug: 16301261
Change-Id: I87a7c808d116c86aa68cebb36631c46d0a54be96

services/devicepolicy/java/com/android/server/devicepolicy/DevicePolicyManagerService.java

index c218d38..2a11252 100644 (file)
@@ -4030,7 +4030,8 @@ public class DevicePolicyManagerService extends IDevicePolicyManager.Stub {
 
     @Override
     public boolean getCrossProfileCallerIdDisabledForUser(int userId) {
-        enforceSystemProcess("getCrossProfileCallerIdDisabled can only be called by system");
+        // TODO: Should there be a check to make sure this relationship is within a profile group?
+        //enforceSystemProcess("getCrossProfileCallerIdDisabled can only be called by system");
         synchronized (this) {
             ActiveAdmin admin = getProfileOwnerAdmin(userId);
             return (admin != null) ? admin.disableCallerId : false;