To read all comments associated with this story, please click here.
If you're going to slam Apple....hit 'em. Don't screw around "gripping your bat".
Sorry, couldn't think of anything batter to say. ;-)
Seriously, when you're an Apple user, sometimes humor is the only response that's appropriate to the atrocious way they handle security.
Meh, I'll do a translation. Apple maybe a great spin bowler on a good day, but when things go bad, its almost a certainty that they'll be hit for a six. They should counting themselves lucky that there are less men on the cricket ground, and the fact that the batter has his mind else where given the game is so low brow.
I don't mean to nitpick (far be it from me!) but since in your analogy Apple is bowling then more men on the field would be an advantage, not a disadvantage. With enough extra men on the ground you could crowd the bat and ring the boundary as well. Might make it hard to hit even the dodgiest delivery for six...
"They are last at bat in the DNS patching game, and when they manage to hit the DNS bug the patch is an easy out."
Apple uses BIND for its DNS server, and a patch for BIND was indeed available but it was buggy. A performance issue was discovered on high-traffic recursive servers, defined as those seeing a query volume of greater than 10,000/queries per second. So yes the official patch for BIND was and is still buggy.
I don't think that Apple would ship a buggy patch for systems in production (open source guys does yes, but well that's their decision...), even if the security threat is high. Shipping buggy code even to fill a security issue is not acceptable.
Apple uses BIND for its DNS server, and a patch for BIND was indeed available but it was buggy. A performance issue was discovered on high-traffic recursive servers, defined as those seeing a query volume of greater than 10,000/queries per second.
Sometimes you got to weigh whether the previous version, which had a serious bug, outweighs the bug in the new version, which has a less serious bug. If you wait to get rid of bugs by waiting for bug-free software, you may wait for a long time...
Also, when Apple did patch it, and they did, with the aforementioned buggy patch, they didn't even patch it properly on the client OS, which is less likely to encounter such a scenario. That in spite of documenting that they *had* patched it, like they had, belatedly, for OS X Server.
Edited 2008-08-04 06:21 UTC




Member since:
2005-07-08
Forgive the baseball analogies non-North-American readers, but Apple is really batting .000 in the security department lately.
They are last at bat in the DNS patching game, and when they manage to hit the DNS bug the patch is an easy out. They make FileVault a shut-out for the hacking team thanks to their censorship, also they send their security engineers back to the bench rather than let them play for the crowd. At Apple, is nobody on at the bottom of the Ninth?
Secrecy is great for an iPod launch, it makes no sense for security. Somebody needs to teach Apple good sportsmanship before the enterprise takes their ball, and goes home.
Edited 2008-08-03 17:47 UTC