How else could he proved that the flaw existed?Well he did create and upload to the store an app that bybassed security and could transmit user data to his private server. That's against the T&C's. Not very clever really.
Describing it in detail would be enough. Apple engineers would be able to test it.How else could he proved that the flaw existed?
Because Apple's interest in talking swiftly, directly and openly to developers is, of course, legendary.Describing it in detail would be enough. Apple engineers would be able to test it.
There is an accepted way of doing this that usually involves telling the company about the flaw, waiting 30 days, then announcing the flaw to the press. What this chap did is not the way to go about things.How else could he proved that the flaw existed?
Charlie Miller, a longtime Mac hacker, has earned himself a bit of notoriety this week by revealing a security hole in iOS and losing his Apple Developer Program license in the process. He managed to identify an exception introduced from iOS 4.3 onwards that allows the browser to run unsigned code in memory, which he then expanded to include other apps, thereby skipping the code-signing check that is fundamental to iOS security. The result, as demonstrated in the video below, is that seemingly benign apps can make use of that exception to download and run unchecked and unauthorized code through the system. ..
Needless to say, this is a pretty major vulnerability in the typically ironclad App Store defenses, and Charlie's decided to keep the particulars of the flaw under wraps until the SyScan conference in Taipei in order to give Apple time to patch the problem. The first response from Cupertino, however, has been to yank Charlie's app from the App Store — understandable, since it is a form of malware — and his name from its Developer Program. The latter move is likely motivated by the fact Charlie opted to publish his findings in app form (and thereby clearly breaking Apple's rules for developers), but it still strikes us as draconian when the man's trying to alert Apple to the problem instead of exploiting it for his own gain.
http://www.theverge.com/2011/11/8/2...-an-ios-app-vulnerability-loses-his-developer
Apple take security flaws seriously.
There's a whole submitting your app process, where the developer could quite easily have pointed it out/raised awareness.
Yeah but that wouldn't give the screaming ninnies something to complain about though would it?
Certainly a lot harder to investigate if Apple PR have buried or spun it away.
How would they do that if the guy that discovered it could just go public anyway?
anything negative about Apple security would be leapt on.
...said some Wired reader.
If I get really negative, perhaps the phone will actually start to recharge itself. In my bare hands!Or your negativity. Its feeding off the bad vibes man.
as any fule noe positivity charges things negativity is draining...If I get really negative, perhaps the phone will actually start to recharge itself. In my bare hands!
Judging by the Apple support forums, the update isn't working for everyone. There's some angry folks on there!Thats 5.0.1, Im glad its available a an over-the-air update since I have numerous devices to support at work and now hopefully users will just do it for themselves.
Thats 5.0.1, Im glad its available a an over-the-air update since I have numerous devices to support at work and now hopefully users will just do it for themselves.