No, of course not, and I'm fully aware of the implications of releasing an untested patch. I've seen 1st hand the results of doing this when I worked for the numerous software houses I've worked at, and especially when I was a consultant at Andersen Consulting/Accenture.
However, I don't consider almost 2 weeks lead time for a critical patch to be acceptable. A fix was (unofficially) available on 1st Jan, and was examined and tested by Sans. The fix itself is not that complicated - it just disables the defunct Escape() function in GDI32.DLL. If this is the same approach that Microsoft have taken with their patch, then the testing of one function should not require in excess of 10 days... especially one that is defunct!
According to MS, the patch is only being released as part of Jan's monthly schedule - I would have deemed it worthy of releasing prior to Patch Tuesday.
Quote:
|
Originally Posted by Microsoft
Microsoft has completed development of the security update for the vulnerability. The security update is now being localized and tested to ensure quality and application compatibility. Microsoftâ₠¬â„¢s goal is to release the update on Tuesday, January 10, 2006, as part of its monthly release of security bulletins. This release is predicated on successful completion of quality testing.
|