- 02 Apr, 2022 1 commit
-
-
vvb2060 authored
-
- 30 Mar, 2022 2 commits
- 28 Mar, 2022 2 commits
- 26 Mar, 2022 8 commits
-
-
LoveSy authored
-
VD $ VD171 @ Priv8 authored
-
VD $ VD171 @ Priv8 authored
-
CDzungx authored
Quick fix: Yes - "Đồng ý" -> "Có" to be more versatile.
-
vvb2060 authored
-
vvb2060 authored
-
topjohnwu authored
-
topjohnwu authored
-
- 25 Mar, 2022 2 commits
- 24 Mar, 2022 2 commits
- 22 Mar, 2022 1 commit
-
-
topjohnwu authored
Close #5620
-
- 21 Mar, 2022 3 commits
-
-
LoveSy authored
-
LoveSy authored
Co-authored-by:
canyie <31466456+canyie@users.noreply.github.com> Co-authored-by:
John Wu <topjohnwu@gmail.com>
-
topjohnwu authored
-
- 20 Mar, 2022 1 commit
-
-
topjohnwu authored
-
- 19 Mar, 2022 3 commits
- 18 Mar, 2022 6 commits
-
-
topjohnwu authored
-
topjohnwu authored
-
topjohnwu authored
-
topjohnwu authored
-
topjohnwu authored
Since Android 13, sepolicy are also loaded from APEX modules. Part of the change is to run restorecon before SELinux is set to enforce. In order to support this situation, we also hijack plat_file_contexts if necessary to properly order our operations. Original idea credits to @yujincheng08, close #5603
-
topjohnwu authored
-
- 17 Mar, 2022 7 commits
-
-
topjohnwu authored
-
topjohnwu authored
-
LoveSy authored
-
topjohnwu authored
Close #5598
-
topjohnwu authored
-
topjohnwu authored
-
topjohnwu authored
On older Android versions, pre-mounting selinuxfs will lead to errors, so we have to use a different method to block init's control flow. Since all devices that falls in this catagory must both: 1. Be Android 8.0 - 9.0 2. Have early mount fstab in its device tree We can actually use the same FIFO trick, but this time not on selinuxfs, but on the read-only device tree nodes in sysfs or procfs. By mocking the fstab/compatible node in the device tree, we can block init when it attempts to do early mount; at that point, we can then mock selinuxfs as we normally would, successfully hijack and inject patched sepolicy.
-
- 16 Mar, 2022 1 commit
-
-
topjohnwu authored
In the current implementation, Magisk will either have to recreate all early mount implementation (for legacy SAR and rootfs devices) or delegate early mount to first stage init (for 2SI devices) to access required partitions for loading sepolicy. It then has to recreate the split sepolicy loading implementation in-house, apply patches, then dump the compiled + patched policies into monolithic format somewhere. Finally, it patches the original init to force it to load the sepolicy file we just created. With the increasing complexity involved in early mount and split sepolicy (there is even APEX module involved in the future!), it is about time to rethink Magisk's sepolicy strategy as rebuilding init's functionality is not scalable and easy to maintain. In this commit, instead of building sepolicy ourselves, we mock selinuxfs with FIFO files connected to a pre-init daemon, waiting for the actual init process to directly write the sepolicy file into MagiskInit. We then patch the file and load it into the kernel. Some FIFO tricks has to be used to hijack the original init process's control flow and prevent race conditions, details are directly in the comments in code. At the moment, only system-as-root (read-only root) support is added. Support for legacy rootfs devices will come with a follow up commit.
-
- 14 Mar, 2022 1 commit
-
-
topjohnwu authored
-