diff options
| author | Michal Karpinski <mkarpinski@google.com> | 2019-04-16 14:02:46 +0100 |
|---|---|---|
| committer | Michal Karpinski <mkarpinski@google.com> | 2019-04-16 15:50:13 +0100 |
| commit | 2927b542ab9d6e63f61c582c6a027da3efd9dead (patch) | |
| tree | 6032710dc8369b13d011850422428e56faa9dd71 /tools/aapt2/format/binary/BinaryResourceParser.cpp | |
| parent | 949305fe52816c6a51454cc8aee56fee8486eeac (diff) | |
Don't allow PI-based starts and trampolines when sender
is SYSTEM_UID and it happens to pass foregroundness check
at the time of sending
It could lead to abuses like directing the user to Settings app
and then giving a PI through any API, so that app could open
activity/trampoline due to Settings app (SYSTEM_UID) being fg.
PI-based starts where sender is SYSTEM_UID will no longer be
supported based on foregroundness check. Any such starts need
to now be explicitly whitelisted (see b/124858756).
Also, ignore windows of type TYPE_APPLICATION_STARTING in
isAnyNonToastWindowVisibleForUid() check.
Bug: 129563343
Test: atest WmTests:ActivityStarterTests
Test: atest BackgroundActivityLaunchTest
Test: atest CtsActivityManagerDeviceTestCases:ActivityStarterTests
Test: atest WmTests:RootWindowContainerTests
Change-Id: I563f71f0b1c7922d8c675d2e4feed909f43446be
Diffstat (limited to 'tools/aapt2/format/binary/BinaryResourceParser.cpp')
0 files changed, 0 insertions, 0 deletions