Apps deliberately refusing to work on modded devices: Difference between revisions
Magnusmaster (talk | contribs) |
Magnusmaster (talk | contribs) mNo edit summary |
||
| Line 2: | Line 2: | ||
==How it works== | ==How it works== | ||
Phones and PCs include a 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-08-03}}</ref>: a chip | Phones and PCs include a 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-08-03}}</ref>: a chip independent from the device's CPU and 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 in any way and in such a case 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== | ||
The owner of the phone is unable to do the following (while continue to use applications that block modded devices) | The owner of the phone is unable to do the following (while continue to use applications that block modded devices) | ||