diff options
| author | Philip P. Moltmann <moltmann@google.com> | 2018-12-07 16:57:38 -0800 |
|---|---|---|
| committer | Philip P. Moltmann <moltmann@google.com> | 2018-12-10 09:01:49 -0800 |
| commit | c6bdbec499d7afd4806e6f472ab049d3b6967764 (patch) | |
| tree | d141913ec816f6962d65d067f2a6c912a0c43a76 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 3159fa2df8057a0e806ce14a0f6d7bfe89615201 (diff) | |
Do not review removed permissions
Removed permissions don't participate in the permission model, hence we
should ignore them everywhere.
The problem was that if we set them as "review-required" other code gets
confused as an app that has been reviewed still has some permissions with
this flag set.
Test: 1. Installed legacy app that needs storage access (verified
permission flags)
2. reviewed permisisons (verified permission flags)
3. reset app (verified permission flags)
atest android.appsecurity.cts.PermissionsHostTest#testCompatDefault22 (while in isolated storage mode)
atest android.appsecurity.cts.PermissionsHostTest#testReviewPermissionWhenServiceIsBound (while in isolated storage mode)
Fixes: 120223984
Change-Id: I4b55cc4fb2e39b358fd3b6c5db600c5b3b927096
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions