diff options
| author | 2022-10-11 16:31:30 -0700 | |
|---|---|---|
| committer | 2022-10-13 14:12:46 -0700 | |
| commit | fd6643e366577d1c2c8bf6f521dc9733e7ffdbd4 (patch) | |
| tree | 072b4b5f074e603563b6eed069811ce6c2d38181 /libs/androidfw/ConfigDescription.cpp | |
| parent | 1b3db4d5aaa7f94d22710111c05d1f8b3bc4197d (diff) | |
Enforce ADJUST_RUNTIME_PERMISSIONS_POLICY
In updatePermissionFlags, we're calling clearCallingIdentity. And,
just after doing so, we're calling
enforceCallingOrSelfPermission(ADJUST_RUNTIME_PERMISSIONS_POLICY).
But, these two things don't really make sense together, because the
former nullifies the latter.
We could either:
1. Remove clearCallingIdentity but keep enforceCallingOrSelfPermission,
or
2. Remove both
For security, this CL goes with the first option. But, doing so means
updatePermissionFlags now enforces ADJUST_RUNTIME_PERMISSIONS_POLICY.
And this breaks some CTS tests. To address this, we have to add
ADJUST_RUNTIME_PERMISSIONS_POLICY to the shell identity.
Bug: 190694761
Test: atest ActivityPermissionRationaleTest
Change-Id: I7031aebf69d9ec919334573b99eb6b7cb8be31d0
Diffstat (limited to 'libs/androidfw/ConfigDescription.cpp')
0 files changed, 0 insertions, 0 deletions