#16 "60+ days to fix it?"
No, it was fixed on the 28th of September, it just wasn't propagated through earlier versions. So it was fixed 52 days before Debian was compromised. The reason it wasn't immediately applied to earlier version is explained in the article:
"Even though this kernel bug was discovered in September by Andrew Morton and already fixed in recent pre-release kernels since October, its security implication wasn't considered that severe. Hence, no security advisories were issued by any vendor. However, after it was discovered to be used as a local root exploit the Common Vulnerabilities and Exposures project has assigned CAN-2003-0961 to this problem. It is fixed in Linux 2.4.23 which was released last weekend and in the Debian advisory DSA 403."
There's also the issue of keeping patches in test kernels separate - although I'm sure that they have learnt from this and in the future will hopefully automatically put out a security advisory.
"Can you say "Security By Obscurity" doesn't work?"
Where was the obscurity? It was noted that this bug exists, it was fixed and the full patch and source code was available since September.... where do you figure the obscurity was? The security problem here was the underestimation of this bug whereby it wasn't deemed important enough to immediately release a patch for. After all, what's to say that the person who compromised Debian didn't get the idea to attack this bug after seeing the notes about it and the fix itself? Sure, whinge about security (which you will anyway) but there's no obscurity here - that's Microsoft's domain!
"Or was Linus was planning an OS X type "Upgrade or else" security patch?"
Get over it, grow up, whatever it takes. No Linus won't charge you $129 to get the patch - if you have an issue with Apple, take it up with them rather than repeating your whinging!
"How many other kernel patches are being held back for no good reason?"
Go through the release notes! If there's bugs that have been fixed in test kernels then you'll have all the information there - what you won't find is the reasons why certain bugs haven't been patched for earlier versions, and those reasons could be like in this case where the bug isn't deemed sever enough (which is dangerous to assume!) or perhaps they are incompatible for whatever reason.
|