[Magisk] pndwal:
Thanks; btw, I'm not dev; just trying to keep up... 😜

Mmm... So I think we're on the same page here... Many means to detect apps.

Ok... Wasn't aware apps detect that way; knew they detected manager which is why they adopted 'parasitic' mode and later invoke manager from notifications...

Point was just that banks are detecting suspicious apps, HMA is effective in these cases so compatibility for LSPosed is essential for HMA.

Isn't that the same thing?... Hiding root from GMS (guessing main process causes the issue) using DenyList, PIF inbuilt hiding, old MagiskHide, DenylistUnmount etc breaks system fonts but Shamiko doesn't...

Ah, thanks for clarifying... I was having trouble understanding that property... But I'm a bit thick... so the real issue is that fonts get unmounted, and app cannot reload because it can't see fonts.xml after fork?...

Again, thanks for valuable insight...

Really I didn't want a new fix, just to know if Shamiko font fix should work if modules are both loaded, ie that the fix won't be overridden/broken by Zygisk Assistant. (?)

Ah yes!... But doesn't include many original MagiskHide sensitive props, mainly only for SafetyNet/PI verdicts, not for specific device or app checks... I think @digeridoohans collection was pretty much complete (from Magisk 23.0):

https://github.com/Magisk-Modules-R...README.md#setreset-magiskhide-sensitive-props

Here's DenyList Unmount modules's config including props for Recovery mode (A9 A-only LV devices w/o B/L support for ramdisk in/boot):

https://github.com/mywalkb/DenylistUnmount/blob/main/magisk/service.sh

What I was proposing was that Zygisk Assistant added all original sensitive props (and new ones that may pop up, needed for A14 etc?) so that it becomes a fairly robust stand-alone solution for Play Integrity MEETS_DEVICE_INTEGRITY with droidguard/attestation (and possibly main) GMS process added to (unenforced) denylist, and root hiding in general, for devices not requiring main PIF functions, eg devices launched prior to Android 8.0 or later devices with broken keymaster/chain of trust implementations like OnePlus...

Glad to hear it's not hard... Please do consider this. 👍

Aside: Of course, for stand-alone use of your module there's enough props set for official LOS ROMs... Users will still generally need to spoof matched fingerprint and security patch date props (eg w/ MHPC module) unless ROM predates March 2018...

Ah... Thanks...

Again, I'm not fully getting the principle here... (Non-coder brain)...

... Think I've I've got it now...

With DenyList, Magisk/modules completely "get out of the way"... I'm assuming that Unmounting natively in KSU is like DenyList (unmounts fully, denying modifications/injection for the app)??

With modules using list as hidelist, Magisk/modules are unmounted for App but not completely (as they can still function and inject code in hidden apps)??... As KSU seems to have no "Enforce DenyList" toggle, we rely on earlier timing to prevent KSU from 'completely unmounting'... Or maybe I'm not understanding 'Unmounting' properly; are modules always fully 'unmounted' and 'denying' is an additional function??

Please edify me! 🙂👍 PW