diff options
| author | Svetoslav Ganov <svetoslavganov@google.com> | 2016-05-05 18:08:00 -0700 |
|---|---|---|
| committer | Svetoslav Ganov <svetoslavganov@google.com> | 2016-05-05 18:21:09 -0700 |
| commit | eaca4c5022fc2bde816ac58fe57d80f7e9706ead (patch) | |
| tree | 09843b320baf339b47b89a1c2eee8fdda3f1e4a0 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | c1ff12eccd0e48ff7feab62387e60ae4010a3cc9 (diff) | |
Properly map runtime permissions to app ops
The code assumed mapping from a permission to an app op
is one to one but this is not always the case. For example,
READ_SMS is mapped to OP_READ_SMS and OP_READ_ICC_SMS which
resulted mapping the READ_SMS permission to the OP_READ_ICC_SMS
instead of OP_READ_SMS resulting in a failure to find the op
name given the permission.
This breaks the AppOpsManager.permissionToOp() API for READ_SMS
returning null instead of OPST_READ_SMS. The consequence of this
is that the apps that proxy permission protected operations may
let the operations for READ_SMS go through as they would get a
null app op, i.e. no app op while there is one and it can be
disabled for the caller.
bug:28620132
Change-Id: I92f8ef375ae2122b7266c50653ce73f3d90f4b28
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions