Re:Reverse-engineering the Starbucks ordering API
by KekDemaga on Wednesday July 12, 2017 @09:18PM
(#14758098)
"2,147,483,647 large coffees? I'd better get to work." - some poor Starbucks employee
Re:Reverse-engineering the Starbucks ordering API
by sashk on Wednesday July 12, 2017 @10:06PM
(#14758253)
This reminded me about call to Starbucks during the iPhone announcement in 2007 -- https://youtu.be/bd6dQmN-mPw?t=34s
Re:Reverse-engineering the Starbucks ordering API
by Jonovono on Wednesday July 12, 2017 @09:27PM
(#14758125)
lol. Reminds me of high school. Constructing a green roof garden. We have the genius (see stupid) idea to go order 20 large waters from McDonalds. They just tell us to drive forward and park. Sure enough, not long later, they bring us 20 large waters!
Re:Reverse-engineering the Starbucks ordering API
by smt88 on Wednesday July 12, 2017 @11:05PM
(#14758437)
An interaction that cost McDonald's under $2 and is something you won't forget and will actually tell others about. Sounds like they got their money's worth.
Re:Reverse-engineering the Starbucks ordering API
by _pmf_ on Thursday July 13, 2017 @03:28AM
(#14759402)
> A real method of securing APIs would be a godsend, but in current tech it's just not possible. This is the one place where mediocre security-by-obscurity is your only choice
It's magically possible when tying it to a payment processor, though.
Re:Reverse-engineering the Starbucks ordering API
by IshKebab on Thursday July 13, 2017 @04:49AM
(#14759748)
What abuse would it be ripe for exactly? I assume the only thing they were trying to prevent is third party apps.
Re:Reverse-engineering the Starbucks ordering API
by bpicolo on Thursday July 13, 2017 @12:37PM
(#14762731)
Say a third party app orders the wrong coffee, or orders too much stuff, etc. There's a real business risk because they have to shell out physical capital to make coffee.
I might be slightly off because thinking about it the app probably requires up-front payment. But either way, fully open APIs can cause problems if they're more meant for internal processes
Re:Reverse-engineering the Starbucks ordering API
by prawks on Thursday July 13, 2017 @02:48PM
(#14764009)
One funny (ab)use case that may not be immediately obvious: any public API that accepts payment for goods via credit card will sooner or later attempt to be used by carders to test purchased/stolen card lists for validity.
Re:Reverse-engineering the Starbucks ordering API
by lsaferite on Thursday July 13, 2017 @06:58PM
(#14766018)
So? You mitigate this on the server since you can never trust the client.
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).
A real method of securing APIs would be a godsend, but in current tech it's just not possible. This is the one place where mediocre security-by-obscurity is your only choice =(