Apps deliberately refusing to work on modded devices: Difference between revisions
m →How it works: may as well while I'm at it |
|||
| Line 3: | Line 3: | ||
==How it works== | ==How it works== | ||
Some phones and PCs include a [[Trusted computing|Trusted Platform Module]] <ref>{{Cite web |title=Trusted Platform Module |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-date=2016 | Some phones and PCs include a [[Trusted computing|Trusted Platform Module]] <ref>{{Cite web |title=Trusted Platform Module |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-date=3 Aug 2016}}</ref>: a chip independent from the device's CPU which can only run software signed by the device manufacturer. This chip allows applications to use a technique called remote attestation to detect if the operating system has been tampered with, and if so will block functionality or refuse to work altogether. If done properly, remote attestation is impossible to spoof, even by the owner of the device. | ||
==Why it is a problem== | ==Why it is a problem== | ||