To read all comments associated with this story, please click here.
No, that's not a fair assessment.
The fact is, Microsoft released the patch before Sasser: It wasn't Microsoft's fault like it was with blaster.
I frankly blaim most of the people who didn't run updates. Not that everyone should have had their updates run already, but I think that before Sasser hit a good 15% of machines should have been updated; and within a week 100% should have been: That would have really brought the damages waaaay down.
But businesses all have so many self-inflicted barriers to running updates. And home users are just too stinkin lazy.
"frankly blaim most of the people who didn't run updates. Not that everyone should have had their updates run already, but I think that before Sasser hit a good 15% of machines should have been updated; and within a week 100% should have been: That would have really brought the damages waaaay down."
From what I read, they were afraid that it will brake
their MS SQL if they apply the said patch. And that
it did happen before. So now we're back to MS's poor
OS design.




Member since:
2005-07-06
if they would admit their track record on security is due to design. I guess it is easier to blame the worm authors than for Microsoft to accept responsiblity for designing a system so easily compromised.
Microsoft is arguably negligent for allowing it to occur, but the the blame for the worms themselves should be placed solely on those who wrote and released them.