Re:Reverse-engineering the Starbucks ordering API
by sowbug on Thursday July 13, 2017 @09:31AM
(#14761035)
You can get pretty far with a secure element. Server challenges with signed payload of nonce + current timestamp, and client verifies it and then re-signs the payload. For something like a third-party coffee-ordering app, the economics of the usual attacks don't scale (either physically tearing apart the chip or exploiting a vulnerability in the first-party app).
[ Parent
| on HN ]
There are no comments on this comment yet.