From 612b51d48f9771a65cfab045f931573f42d3a494 Mon Sep 17 00:00:00 2001 From: topjohnwu Date: Fri, 13 Mar 2020 01:48:14 -0700 Subject: [PATCH] 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. --- native/jni/core/db.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/native/jni/core/db.cpp b/native/jni/core/db.cpp index 8a559c879..12baa732d 100644 --- a/native/jni/core/db.cpp +++ b/native/jni/core/db.cpp @@ -115,7 +115,7 @@ db_settings::db_settings() { data[ROOT_ACCESS] = ROOT_ACCESS_APPS_AND_ADB; data[SU_MULTIUSER_MODE] = MULTIUSER_MODE_OWNER_ONLY; data[SU_MNT_NS] = NAMESPACE_MODE_REQUESTER; - data[HIDE_CONFIG] = true; + data[HIDE_CONFIG] = false; } int db_settings::getKeyIdx(string_view key) const {