Magisk/app
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
..
src Application Component Granularity MagiskHide 2019-03-01 17:08:08 -05:00
.gitignore Separate backend logic from frontend UI 2018-12-13 04:35:50 -05:00
build.gradle Upgrade dependencies 2019-02-28 23:42:33 -05:00
proguard-rules.pro Fix snet on release builds 2019-02-01 06:21:55 -05:00
README.md Update Magisk Manager README 2018-08-30 04:03:14 -04:00

Magisk Manager

This repo is no longer an independent component. It is merged into the Magisk Project.

Translations

The default (English) strings are mainly in src/full/res/values/strings.xml; some are scattered in src/main/res/values/strings.xml and src/stub/res/values/strings.xml.
Translations are highly appreciated via pull requests here on Github.
Place translated XMLs in the corresponding locale folder.