2 ms·
Besides it maybe not being Apple’s fault (except for not telling anyone) - it is maybe Apple’s fault because they explicitly state they are reviewing apps, and
by lazide 6y ago
Besides it maybe not being Apple’s fault (except for not telling anyone) - it is maybe Apple’s fault because they explicitly state they are reviewing apps, and did not catch this issue. So they obviously have a huge blind spot and their customers were impacted because of it. Considering the scope and scale of the App Store and the massive revenues from it, it is also pretty hard to believe some better scanning or analysis software wouldn’t have caught this pre-emptively?
Since I remember the ‘Apple was not doing true binary level review’ coming up when I talked to an iOS developer literally a decade ago about the App Store (back in Android 1.1 SDK days) - he even mentioned this type of attack as a possibility - and they obviously haven’t changed that, there are probably a ton more like this out there that have slipped under the radar due to smaller scope, or less clear impact.
- harikb 6y agoShort of Apple proxying and reviewing every byte sent out by an app, I just don’t see how this level of review is possible. It is like detecting virus or malware. Whether apple should have boasted about their review process or not is another matter. There is no technology we have today, whether it is mobile, server side, Linux kernel or whatever that accepts random code from strangers (that is what you doing with pirated s/w) and detects intentionally written malicious code.
- josephcsible 6y agoThe point is that Apple pretends that there is such a thing, but that it only works if they have a walled garden.
- FireBeyond 6y agoSure. And what prevented Apple from telling those users their security had been compromised? Not much beyond a desire to not make a lie of their "curated, secure walled garden" PR.