The fact still remains that Microsoft is NOT to blame for this.falcone said:they always make yopu feel "hey, they are finally doing something..", but then soon enough, another virus exploits the service pack and the whole world screams...
X-Istence said:Hmmm, lets see.
Programmers list of todo's:
Bug in ssl code in Windows (Status: Fixed; Time: 6 months)
Patch for MSSQL (Status: Fixed; Time: 2 Months)
Ah, i could keep on going.
Also, Netryder if it is it the users fault, then MS doesnt take any of the blame, however they are to blame. They wrote buggy code, and untested released it to the public. The same happens with free software, and they always take the blame for it. They always say, sorry we were wrong, here is the patch, please update your systems.
Whereas with Windows everyone just pushes it onto the end users instead of MS, which in this case did release a patch, but didnt even bother to test the product before releasing it. Even the open source movement makes stupid mistakes, but none as big as Nimda, Code Red and varies others. There is no exploit yet to automatically thru some bad coding install a backdoor and start mass mailling and take out an entire internet backbone cause of the flooding of traffic. I have yet to see thousands and thousands of boxen hitting each other with all kinds of reqeusts on the MySQL or PostGreSQL port cause its vulnerable.
And the windows auto update feature breaks as well. I have had a box grab an update that was available for something, installed it, and a few hours later it was pulled and then a new one was put up cause the old one was broken. In the mean time i had rebooted and my box wouldnt come back up again. THAT is why a lot of poeple turn it off as well. And the phoning home part. I dont know what to think about it. I personally like to know what is doing what at what time and where it is going on the internet. Personally, i also like to install the updates myself so i know what is going on, i like to be in control.
Also note, that in an business enviroment you dont suddenly just roll out a patch. You first test it on the dev boxes, put it under stress to make sure all works correctly, and most boxes that ran MSSQL and others cant be taken offline, they are mission critical servers, and thus the patches are mostly on a 6 month cyle. Every 6 months all the new patches and everything are installed, and then it wont be touched for another 6 months.