Content deleted Content added
Alexceltare2 (talk | contribs) added more details |
Alexceltare2 (talk | contribs) more links |
||
Line 8:
Due to this, some consider this a monopolistic practice deterring the entrance of competing [[mobile operating system]]s in the market. <ref>{{cite web |last1=Schwab |first1=Andreas |last2=Echeverria |first2=Pablo Arias |title=Time to restore fairness and contestability in digital markets |url=https://www.euractiv.com/section/digital/opinion/time-to-restore-fairness-and-contestability-in-digital-markets/ |website=www.euractiv.com |date=24 March 2022}}</ref>
[[Remote attestation|Attestation]] requires a network connection for Google Play Services to connect to Google servers and validate the hardware signatures. Amongst the checks, the API looks for bootloader unlock status, ROM signature and kernel strings. Upon successful checks, [[Google Play]] will mark the device as ''Certified''.
The SafetyNet Attestation API (one of the four APIs under the SafetyNet umbrella) has been deprecated.<ref name="timeline">{{Cite web|title=SafetyNet Deprecation Timeline|url=https://g.co/play/safetynet-timeline|website=Android Developers|language=en-US}} {{Retrieved|access-date=2023-10-06}}</ref> {{As of|2023|10|6|post=,}} Google expects to fully replace it with the '''Play Integrity API''' by the end of January 2025.<ref name="timeline"/><ref>{{cite web |title=Migrating from the SafetyNet Attestation API {{!}} Google Play |url=https://developer.android.com/google/play/integrity/migrate |website=Android Developers |language=en}}</ref> Like the SafetyNet APIs, the Play Integrity API is offered by Google Services and thus is not available on free Android environments ([[Android Open Source Project|AOSP]]). Therefore, apps that require the API to be available may refuse to execute on AOSP builds.
Line 14:
== See also ==
* [[Samsung Knox]]
* [[Trusted Computing]]
== References ==
| |||