Disable MagiskHide by default
Since SafetyNet CTS is impossible to achieve, leaving MagiskHide on by default no longer serves a purpose. For more details regarding the latest SafetyNet changes, please check: https://twitter.com/topjohnwu/status/1237656703929180160 https://twitter.com/topjohnwu/status/1237830555523149824 MagiskHide's functionality will continue to exist within the Magisk project as it is still extremely effective to hide modifications in userspace (including SafetyNet's basicIntegrity check). Future MagiskHide improvements _may_ come, but since the holy grail has been taken, any form of improvement is now a very low priority.
This commit is contained in:
parent
8101f3f67d
commit
612b51d48f
@ -115,7 +115,7 @@ db_settings::db_settings() {
|
|||||||
data[ROOT_ACCESS] = ROOT_ACCESS_APPS_AND_ADB;
|
data[ROOT_ACCESS] = ROOT_ACCESS_APPS_AND_ADB;
|
||||||
data[SU_MULTIUSER_MODE] = MULTIUSER_MODE_OWNER_ONLY;
|
data[SU_MULTIUSER_MODE] = MULTIUSER_MODE_OWNER_ONLY;
|
||||||
data[SU_MNT_NS] = NAMESPACE_MODE_REQUESTER;
|
data[SU_MNT_NS] = NAMESPACE_MODE_REQUESTER;
|
||||||
data[HIDE_CONFIG] = true;
|
data[HIDE_CONFIG] = false;
|
||||||
}
|
}
|
||||||
|
|
||||||
int db_settings::getKeyIdx(string_view key) const {
|
int db_settings::getKeyIdx(string_view key) const {
|
||||||
|
Loading…
Reference in New Issue
Block a user