![]() ![]() Yeah, we've all been aware of this for some time, but it really changes nothing regarding device integrity attestation APO implementations or use. ![]() Moreover, Strong Integrity practically equals to CTS Hardware Attestation (read Google tech docs, they have been posted and discussed here on XDA a year ago, they have even a chart how to compare SN and PI levels) hence developers who wanted, could have required CTS Hardware Attestation with SafetyNet if/when they wanted two years ago - did they? One has to properly use DenyList/MagiskHide/UnmountModules, Shamiko (if using Zygisk), HMA, or switch to Riru (and Delta or Alpha fork of Magisk) instead of Zygisk and those banking apps will no more detect/complain/force-close although Strong Integrity would still be failing Some apps detect further hints or artefacts of root but those are absolutely not related to Strong Integrity. ![]() We know (for sure) only for one or maybe two/three apps (you never know since the app does not tell you what they detected) that require Strong Integrityįor all others apps, Basic and Device Integrity are enough. Google themselves, a year ago or so, switched from SafetyNet to PlayIntegrity for Google Wallet but Wallet requires ONLY Device and Basic Integrity, never Strong Integrity Strong Integrity is just one of three (four if counting also Virtual Integrity) tiers of Play Integrity Strong Integrity does not equal to Play Integrity. Please read again and better understand things Deprecating SafetyNet (by the way, notes from Google are around for more than a year, so your 'news' is nothing really new) and replacing by Play Integrity DOES NOT FORCE anyone and by an means to require Strong Integrity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |