Right. This is basically Apple violating their own "responsible disclosure" policy and announcing a 0-day vulnerability in OS X.
They should have delayed the release of the iOS patch until the OS X one was ready. This is the whole point of responsible disclosure: maybe the vulnerability is being used in the wild, but by delaying release of it until the vendor can patch it, the potential for expoitation is greatly reduced.
>All this did was make more people aware of it, and only then for a few days.
You say that as if it's not a big deal...
There is no justification for this bug. It never should have shipped. It never should have gone unnoticed for so long. It never should have been announced prior to a patch being available.
No matter how you slice it, Apple failed miserably, and "iOS was probably being exploited" is not an excuse. Apple has how much money? How much money do you think it costs to put their entire Core OS engineering staff on SHIPPING AN UPDATE FOR BOTH OPERATING SYSTEMS?
They could have afforded it. They were simply too incompetent, after a chain of incompetence, to do so.
Don't cargo cult 'common wisdom'; the only incompetence on display here is your axiomation of things you don't understand.
Stop trying to acquire internet points by being a jerk.
Please have the bridge delivered to my home between noon and six.
(Though, really, I should just accept this absurd statement, since it amounts to you admitting your own incompetence.)
> Stop trying to acquire internet points by being a jerk.
This from the guy who decided his scintillating contribution to the thread would be redundantly accusing people of "apologism" and "incompetence". You do understand the people who actually do work at Apple are human beings, and that you are flinging insults at them, right?
Why? Do you not already have a bridge to troll under?
> You do understand the people who actually do work at Apple are human beings, and that you are flinging insults at them, right?
Yes, and I know who they are.
If this is true, then their process could use some adjustment. Contrast with Google Chrome which has the regular motion of changes going through channels, but the ability to update virtually all clients within a matter of hours if a critical issue is found.
(I realize there is a lot more QA necessary for an OS update, but I'm not convinced that a fix for this specific bug would have taken a long time to QA. Certainly not anywhere near as long as we've waited for this update, or as long as a lot of people will delay installing it because it is huge.)
To play the devil a bit, their process still needs some work, there isn't a good reason why they couldnt have released this patch in its own approval process simultaneously with a higher priority for staff to choose it over facetime.
The only alternative would have been to delay the iOS release, which they didn't do because almost certainly this bug was already being exploited in the wild. All this did was make more people aware of it, and only then for a few days.
As for OS X release, I'm sure they released it as fast as they could. It has nothing to do with releasing along with FaceTime integration, and everything to do with 10.9.2. was already going through the GM process, and it was faster/easier to add this fix into that and continue trying to validate the GM than it was to spin up an entirely new train for a 10.9.1.1 with just this fix and try to validate that.