Minor reduction of confusion re Magisk v23/24 #235
Conversation
|
There is no need to use MagiskHide Props Config. |
|
We generally won't need to set fingerprint any longer to pass CTS Profile match for either old S/N or new PI deviceIntegrity even in custom, China region, developer, beta uncertified ROMs etc w/ USNF 2.4.0 because we now have mismatched but passing fingerprint set for gms natively (to bypass hardware evaluation type enforcement in some devices for PI deviceIntegrity verdict) and working (passing) for all devices I'm aware of, so readme wording does need adjusting...
This statement is false however; while @Didgeridoohan hasn't updated it lately (and is busy with life) MHPC certainly still works fine W/ Magisk 24+!!!... The linked issue is only asking for module update notification support (ie. an enhancement) since we got JSON based updates instead of notifications through old repo... MHPC can still be used with no inherent problems w/ latest Magisk and may still be useful in some edge cases, I don't know, but the statement "MagiskHide Props Config is an easy way to do so on Magisk v23 and older" will only cause confusion. Further, w/ native fingerprint spoofing the statement "You must already be able to pass basic CTS profile attestation" will no longer apply as even devices that couldn't pass with fallback and bypasses allowing Basic evaluation type use will generally pass with this addition... |
|
OP here. Thanks @pndwal ! I can confirm that I was unintentionally mistaken, and this PR is NOT to be merged. Thanks! |
|
Let's continue future discussion at #255 |
👍 ... Well this was already merged on Jan 7... (See above; go to README.md line 7 re. Magisk 23 etc.) Of course MHPC now serves no purpose with USNF, so this all needs rewording again anyway... 😜 |
MagiskHide Props Config does not support Magisk v24, so it may be worthwhile mentioning to the newer users.
Related issue