Magisk: Bring back MagiskHide enabled by default

Created on 13 Mar 2020  路  12Comments  路  Source: topjohnwu/Magisk

As of right now we are not entirely sure what the final state of CTS is going to be. Some users are reporting they are once again passing when they had started failing.

In addition, basicIntegrity is still fooled by magiskhide (which some apps only check that not CTS) and some apps don't rely on Safety net at all.

However in 612b51d48f9771a65cfab045f931573f42d3a494 you have changed default magiskhide behavior. I think at the very least that commit needs reevaluating.

My preferred solution is to ask the user of magisk manager first run

wontfix

Most helpful comment

I feel like it was a warning shot from Google, and maybe MagiskHide should stay disabled by default to help appease them. :grinning:

All 12 comments

We all know Google loves to roll things out, roll it back, roll it out, change it, and then forget it, then roll out something different. We should probably wait to see what the final product will be

Looks like the roll it back part came true. I have not done anything since last night when cts profile was failing and today me and other people are seeing that it is passing.

An assigned was added to the issue on the issue tracker.
https://issuetracker.google.com/issues/151316418

I feel like it was a warning shot from Google, and maybe MagiskHide should stay disabled by default to help appease them. :grinning:

It is very clear at this point that Google is willing to use key attestation for SafetyNet checks, I don't see a point fighting a non winning battle.

The functionality is not removed, it is just no longer enabled by default, as I do want to let people understand that this will not stay long.

It is very clear at this point that Google is willing to use key attestation for SafetyNet checks, I don't see a point fighting a non winning battle.

The functionality is not removed, it is just no longer enabled by default, as I do want to let people understand that this will not stay long.

Nonetheless every app that doesn't use CTS checking will still pass with Hide on. People will not understand why now _every_ app detects root by default.
In addition the new CTS checking only checks bootloader status not actual root, which Hide is still useful for

If you care about hide just turn it on...

Cleaned up and pinned to catch any further development discussion/issue duplicates 馃憤

Also irritating enough it shuts it off if I had it on.
As I own a OnePlus device and hardware attestation was never an issue anyway that's highly annoying to have to find out why safety net it suddenly tripped especially if I didn't already know this changed behavior

That shouldn't be the case.. I'm on latest Canary and MagiskHide has never shut itself off.

Every time I reflash magisk it does that

Every time I reflash magisk it does that

Uh, not intended. Works fine here. Try a clean flash of Magisk with Manager uninstalled and /data/adb empty. Probably some db issue.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

guitardedhero picture guitardedhero  路  3Comments

georgekav2 picture georgekav2  路  3Comments

Ralozey picture Ralozey  路  4Comments

koffiato picture koffiato  路  4Comments

ThiefMaster picture ThiefMaster  路  3Comments