github
/
Magisk
mirror of https://github.com/topjohnwu/Magisk
1
Fork 0
Code Releases Activity
6,144 Commits 3 Branches 132 Tags 108 MiB
Commit Graph

18 Commits

Author SHA1 Message Date
topjohnwu 4e2b88b3d0 Rename rules to preinit 
It is possible that we will allow more preinit files for modules.
Rename the partition and folders from rules to preinit.
 2023-03-21 00:40:11 -07:00
LoveSy 7048aa1014 Rename sepolicy.rules -> rules 2023-03-21 00:40:11 -07:00
vvb2060 978216eade local module: filter hidden dirs 2022-10-03 14:20:09 -07:00
topjohnwu 05e5ac2ad2 Bump min version to v22 2022-06-01 03:05:29 -07:00
南宫雪珊 580c993c0b
Display module status 2022-05-29 01:40:20 -07:00
topjohnwu 3bcaf0ed5b Move more files into core 2022-05-25 05:48:02 -07:00
topjohnwu cc79a96fa3 Update libsu 2022-05-03 01:25:26 -07:00
topjohnwu 71e37345b4 Update libsu 2022-02-28 20:14:58 -08:00
topjohnwu 761a8dde65 Slightly change update UI logic 2022-01-21 05:37:47 -08:00
topjohnwu a73acfb9c2 Show unloaded Zygisk modules in UI 2022-01-21 05:37:47 -08:00
LoveSy 97da7f9691 Do not trust format of 3rd party json 2022-01-20 02:02:39 -08:00
vvb2060 bc0c1980db Support modules update 2022-01-18 02:02:41 -08:00
topjohnwu ddd153c00d Show module suspend notice 
Close #4862
 2021-11-09 23:59:37 -08:00
topjohnwu 067248da75 Cleanup RvItems 2021-09-01 01:17:27 -07:00
vvb2060 350144df29 Do not allow remove the module to be updated 2021-08-29 11:35:46 -07:00
topjohnwu 5ce29c30d2 Fix sepolicy copying 2021-01-10 20:16:02 -08:00
topjohnwu 16e4c67992 Significantly broaden sepolicy.rule compatibility 
Previously, Magisk uses persist or cache for storing modules' custom
sepolicy rules. In this commit, we significantly broaden its
compatibility and also prevent mounting errors.

The persist partition is non-standard and also critical for Snapdragon
devices, so we prefer not to use it by default.

We will go through the following logic to find the best suitable
non-volatile, writable location to store and load sepolicy.rule files:

Unencrypted data -> FBE data unencrypted dir -> cache -> metadata -> persist

This should cover almost all possible cases: very old devices have
cache partitions; newer devices will use FBE; latest devices will use
metadata FBE (which guarantees a metadata parition); and finally,
all Snapdragon devices have the persist partition (as a last resort).

Fix #3179
 2020-11-02 23:20:38 -08:00
topjohnwu 0a14f43f9c Refactor class names 2020-10-10 22:40:57 -07:00