- 01 Jul, 2020 1 commit
-
-
waffshappen authored
Due to the accidental safety>N<et the release build would fail with XLint complaining about a missing default translation. Correcting this to be in line with the actual translation fixes the build error. Xlint Error in Question: ```res/values-in/strings.xml:106: Error: "safetyNet_api_error" is translated here but not found in default locale [ExtraTranslation] <string name="safetyNet_api_error">Kesalahan API SafetyNet</string>```
-
- 30 Jun, 2020 3 commits
- 29 Jun, 2020 5 commits
- 28 Jun, 2020 2 commits
-
-
Shaka Huang authored
Fix crash in #2900 Signed-off-by:
Shaka Huang <shakalaca@gmail.com>
-
topjohnwu authored
-
- 27 Jun, 2020 4 commits
-
-
Ilya Kushnir authored
-
Fox2Code authored
- Thank Diareuse for helping me
-
Shaka Huang authored
Signed-off-by:
Shaka Huang <shakalaca@gmail.com>
-
vvb2060 authored
-
- 25 Jun, 2020 3 commits
-
-
mustafairaqi8 authored
-
Viktor De Pasquale authored
Close #2903
-
topjohnwu authored
-
- 21 Jun, 2020 3 commits
- 20 Jun, 2020 8 commits
-
-
YFdyh000 authored
-
topjohnwu authored
-
topjohnwu authored
-
vvb2060 authored
-
topjohnwu authored
All canary builds will be debug only
-
Albert I authored
Signed-off-by:
Albert I <kras@raphielgang.org>
-
Peter Meiser authored
-
Chris Renshaw authored
- LOS Recovery can't decrypt or even mount /data, thus the installer can't do everything it needs to do and must abort, so also suggest uninstall via Manager at that point - fix removal of addon.d script when uninstall is run via Manager on SAR - fix removal of addon.d with dynamic/logical partitions via mapper
-
- 19 Jun, 2020 3 commits
-
-
topjohnwu authored
Due to changes in ec3705f2, the app can no longer communicate with the dameon through a socket opened on the daemon side due to SELinux restrictions. The workaround here is to have the daemon decide a socket name, send it to the app, have the app create the socket server, then finally the daemon connects to the app through the socket.
-
topjohnwu authored
-
topjohnwu authored
-
- 17 Jun, 2020 4 commits
- 04 Jun, 2020 1 commit
-
-
topjohnwu authored
Introduce new domain `magisk_client` and new file type `magisk_exec`. Connection to magiskd's always-on socket is restricted to magisk_client only. Whitelisted process domains can transit to magisk_client through executing files labelled magisk_exec. The main magisk binary shall be the only file labelled as magisk_exec throughout the whole system. All processes thus are no longer allowed to connect to magiskd directly without going through the proper magisk binary. Connection failures are silenced from audit logs with dontaudit rules, so crazy processes which traverse through all unix domain sockets to try connection can no longer check logcat to know the actual reason behind EACCES, leaking the denied process policy (which is u:r:magisk:s0). This also allows us to remove many rules that open up holes in untrusted_app domains that were used to make remote shell work properly. Since all processes establishing the remote shell are now restricted to the magisk_client domain, all these rules are moved to magisk_client. This makes Magisk require fewer compromises in Android's security model. Note: as of this commit, requesting new root access via Magisk Manager will stop working as Magisk Manager can no longer communicate with magiskd directly. This will be addressed in a future commit that involves changes in both native and application side.
-
- 03 Jun, 2020 3 commits