- 30 May, 2020 3 commits
-
-
vvb2060 authored
-
osm0sis authored
- legacy devices brought up to Android 10 may now use a compressed dt in a hdr_v0 AOSP dt variant extra section, so detect, decompress and recompress this - so far these have only been done using lz4 compression (latest format revision magic), e.g. LOS 17.1 victara (Moto X)
-
topjohnwu authored
-
- 29 May, 2020 1 commit
-
-
topjohnwu authored
-
- 25 May, 2020 2 commits
- 24 May, 2020 2 commits
-
-
topjohnwu authored
For match-all-type rules (e.g. "allow magisk * * *" used in Magisk), we used to iterate and apply rules on all existing types. However, this is actually unnecessary as all selinux types should have at least 1 attributes assigned to it (process types "domain", file context types "file_type" etc.). This means in order to create rules that applies to all types, we actually only need to create rules for all attributes. This optimization SIGNIFICANTLY reduces the patched sepolicy that is loaded into the kernel when running Magisk. For example on Pixel 4 XL running Android R DP4, the sepolicy sizes are patched (before) : 3455948 patched (after) : 843176 stock : 630229 The active sepolicy size actually impacts the performance of every single operation in the operating system, because the larger the policies gets, the longer it takes for the kernel to lookup and match rules.
-
topjohnwu authored
-
- 23 May, 2020 4 commits
- 22 May, 2020 1 commit
-
-
topjohnwu authored
- Update help message to match the spec - Make tokenization not seg fault in certain conditions - Moar template + macro magic to reduce boilerplate
-
- 21 May, 2020 1 commit
-
-
topjohnwu authored
-
- 19 May, 2020 3 commits
-
-
topjohnwu authored
It is possible that a module is breaking the device so bad that zygote cannot even be started. In this case, system_server cannot start and detect the safe mode key combo, set the persist property, and reboot. Also on old Android versions, the system directly goes to safe mode after detecting a key combo without rebooting, defeating the purpose of Magisk's safe mode protection if we only check for the persist property. Directly adding key combo check natively in magiskd allows us to enter Magisk safe mode before the system is even aware of it.
-
Chris Renshaw authored
-
topjohnwu authored
-
- 18 May, 2020 8 commits
- 17 May, 2020 5 commits
-
-
Tornike Khintibidze authored
-
topjohnwu authored
-
topjohnwu authored
-
topjohnwu authored
-
Hen Ry authored
-
- 16 May, 2020 1 commit
-
-
topjohnwu authored
-
- 10 May, 2020 2 commits
- 09 May, 2020 3 commits
-
-
Chris Renshaw authored
-
Chris Renshaw authored
-
vvb2060 authored
-
- 08 May, 2020 4 commits
-
-
topjohnwu authored
-
topjohnwu authored
-
topjohnwu authored
When detecting device is booting as Safe Mode, disable all modules and MagiskHide and skip all operations. The only thing that'll be available in this state is root (Magisk Manager will also be disabled by system). Since the next normal boot will also have all modules disabled, this can be used to rescue a device in the case when a rogue module causes bootloop and no custom recovery is available (or recoveries without the ability to decrypt data).
-
topjohnwu authored
-