summaryrefslogtreecommitdiff
path: root/rs/java/android/renderscript/ProgramFragmentFixedFunction.java
diff options
context:
space:
mode:
authorYohei Yukawa <yukawa@google.com>2018-08-24 09:36:15 -0700
committerYohei Yukawa <yukawa@google.com>2018-08-24 09:36:15 -0700
commit12ec0751348080834debfd2880faeb166954f9cb (patch)
tree31b493031b4f69e2bf1747c62303ad8b56e2c09e /rs/java/android/renderscript/ProgramFragmentFixedFunction.java
parent0cf90160c6948df621b15dd07e007d69a7ad1a1b (diff)
Remove IInputMethod.attachToken(IBinder) from greylist
Apps can never directly use IInputMethod.attachToken(IBinder) in a meaningful way, because 1. The real binder object is always instantiated in the IME process and its proxies will never be exposed to any other process except for the system server process. Even if there was actually a real use of this method (via reflection), then the caller must have been the same IME process. 2. However, InputMethodImpl.attachToken(IBinder) does nothing if it gets called twice for security reasons, because the fact it can be called only once is guaranteed in the protocol between IME and InputMethodManagerService. This means that even if an IME somehow called this Binder method via reflection, it must be either no-op (if it's a secondary call) or make itself useless (if it's the first call). Therefore having this entry hiddenapi-light-greylist.txt must be either a mistake or no-op. Bug: 112722706 Test: compile Test: atest CtsInputMethodTestCases CtsInputMethodServiceHostTestCases Change-Id: Ie5e5b3a5f379c42cf2d5f681b556c60aeccee9f9
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions