What If Microsoft Released Untested Patches?
The other way to examine the benefit of “patches in hours” is to imagine Microsoft doing the same thing. A developer completes his proposed patch. As soon as the patch passes to the testers, the MSRC also posts it for customers to use at their own risk, along with a security bulletin noting that it has not yet been regression or compatibility tested. In theory, this is completely feasible for Microsoft, if almost all customers really wanted it and were willing to take the risk. Keep in mind that the security bulletin with the patch would make the issue very public, so everyone would really hope that the untested patch worked. Does this seem like a process that many customers are yearning for? I can say from my experience that it is the opposite of what customers want.
Related Questions
- Microsoft has released Service Pack 3 for Visual Studio 97 and related products. If I am using VF V5 , should I install this?
- Does OFP: Resistance install all official addons made available in previously released upgrade patches?
- What’s Microsoft’s response to the availability of third party patches for the WMF vulnerability?
