topjohnwu b1afd554fc Application Component Granularity MagiskHide ... Before switching to the new MagiskHide implementation (APK inotify), logcat parsing provides us lots of information to target a process. We were targeting components so that apps with multi-processes can still be hidden properly. After switching to the new implementation, our granularity is limited to the UID of the process. This is especially dangerous since Android allow apps signed with the same signature to share UIDs, and many system apps utilize this for elevated permissions for some services. This commit introduces process name matching. We could not blanketly target an UID, so the workaround is to verify its process name before unmounting. The tricky thing is that any app developer is allowed to name the process of its component to whatever they want; there is no 'one rule to catch them all' to target a specific package. As a result, Magisk Manager is updated to scan through all components of all apps, and show different processes of the same app, each as a separate hide target in the list. The hide target database also has to be updated accordingly. Each hide target is now a <package name, process name> pair. The magiskhide CLI and Magisk Manager is updated to support this new target format.		2019-03-01 17:08:08 -05:00
..
full	Application Component Granularity MagiskHide	2019-03-01 17:08:08 -05:00
main	Add DirectBoot support to receivers and SuRequestActivity	2019-02-04 01:58:04 -05:00
stub	Fix stub compile error	2019-01-08 04:27:55 -05:00