[Magisk] pndwal:
Well I started (there)... So I'll finish (here) then...

Much of your conjecture is really irrelevant here [Edit: not sure about here, however I still don't intend to go there...] but I'll touch on a few points...

In essence, what my response (with references regarding TEE etc here: https://xdaforums.com/t/discussion-play-integrity-api.4479337/post-87393295 ) established is that the security model for many OS's, especially mobile ones incl. other than Android, now includes hardware based attestation to a certified and unmodified runtime environment... This is quite standard and is also the emerging model for PCs and other computing platforms... Actually, much of my point was that Google have been both slow and arguably half-hearted in their implementation of such 'zero trust' protection protocols compared to their competition...

Google is a big corporate player, and as such must keep partners / customers happy to remain viable which means being competitive and providing the secure platform for running proprietary code that banks and other app developers expect these days ... And this includes modern verified boot and other attestations for app providers to be confident that their code can't be abused...

These really have more right to decline to allow their code to run in unexpected/ modified environments as owners of this intellectual property than you do to insist that they stop preventing you...

Google is simply supplying the same attestations and assurances of device / system security that other mobile OS's supply; actually they're dragging their feet in this regard really, and I believe that this is precisely because they are NOT trying to stymie the modding community (described by their own engineers as 'white hat' and 'not nefarious'); they're doing just enough to offer a 'secure operating environment' for 3rd party code, but they know full well how easily their security measures can be subverted and are being bypassed... (Perhaps they just want to be ready for the time when push becomes shove!?)

I think @m0han pointed out that Google was founded well before that ...

Cos they're not against custom mods... or root for that matter!... They're happy for you to have a yellow, orange or red boot state... They're just against you spoofing green!

Also, by your reckoning, heaps of Googlers (google coders and engineers, their own 'flock') must be bent!...

Has iOS?

Why do you assume the worst?? ... TJW likes coding and custom modding, and Android for this reason; Google never said they want to stop modifications to android! Why do you think they do?... They love it!... They know a good thing, even if they've made mistakes before...

Just when Kondik though CyanogenMod was dead cos Google told him to cease and desist packaging GApps, they basically said "no... don't stop with you project... Just don't package our code... but let's do this; let's allow users to 'sideload' GApps themselves cos they've got licenced devices... And someone can package to them to make your life easier too... as long as these are separate from your ROMs, OK?... And very sorry to scare you mate!... You're doing a wonderful job... (ouch!)".

Why do you think they even allow non-certified devices to be white-listed to enable owners to load their proprietary GApps quite legitimately, but stipulate that this is only for custom ROM use?... (Cos they're not against modders ... or OEMs for that matter... but they're against unscrupulous re-sellers etc.)

Come on... That's standard fare mate... It's called proprietary code... Pretty much all commercial code is hidden with various degrees of difficulty to reverse engineer...

We're just lucky Google (as the guardians / creators of the OHA) make Android available as AOSP (Open Source Project)... Should we expect to be able to decode their proprietary / safeguarded code and apps any more than other software vendors just cos they produce all the milestones for and supply AOSP?...

AOSP is their gift... GApps are their bread and butter...

Further, with projects like Treble they're paving the way for easier implementation of custom ROM iterations (as well as OEM upgrades) including use of proprietary blobs (hardware drivers etc) and other OEM closed-source code without the need for reverse engineering or blind configuration attempts... Such initiatives are already benefiting custom Devs and modders... They also distinguish Android as The mod-friendly OS...

Well ... 🙃

✌️PW