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

..

daemon.hpp

Update --remove-modules implementation

2020-10-11 18:30:03 -07:00

db.hpp

Small native code reorganization

2020-03-09 01:50:30 -07:00

flags.hpp

Better logging system

2020-06-01 04:15:37 -07:00

magisk.hpp

Significantly broaden sepolicy.rule compatibility

2020-11-02 23:20:38 -08:00

magiskpolicy.hpp

Support new sepolicy rules

2020-05-25 02:09:43 -07:00

resetprop.hpp

Update resetprop to partially use system impl

2020-05-07 23:54:00 -07:00

socket.hpp

Use FIFO for su request communication

2020-09-10 00:38:29 -07:00