Slashdot Mirror
Microsoft Says Two Basic Security Steps Might Have Stopped Conficker
coondoggie writes "If businesses and consumers stuck to security basics, they could have avoided all cases of Conficker worm infection detected on 1.7 million systems by Microsoft researchers in the last half of 2011. According to the latest Microsoft Security Intelligence report, all cases of Conficker infection stemmed from just two attack methods: weak or stolen passwords and exploiting software vulnerabilities for which updates existed."
It's nothing like the Windows situation where you get a bag of critical patches forced down your throat every Patch Tuesday, and then your Windows box loves to reboot right in the middle of whatever you are doing. Sheesh.
No possible way to construe that as a troll, it is a fact. About Windows. The worst operating system ever forced on the world by illegal means.
When all you have is a hammer, every problem starts to look like a thumb.
Yes, because it's completely impossible to turn that feature off. Oh wait...
http://windows.microsoft.com/en-US/windows7/Turn-automatic-updating-on-or-off
If you don't want them "forced down your throat", maybe you should change the setting to instead notify you that they exist and then let you pick and choose which ones you want to install as well as those you want to ignore permanently? How is that any different from any of the automatic update services in Linux distributions bugging you to update and you continually ignoring them?
I use Windows maybe twice a year and I am not going spend hours fiddling with settings just for that. On Linux it Just Works[tm] and I usually do not have to reboot, even on the rare occasions there is a critical patch.
When all you have is a hammer, every problem starts to look like a thumb.
Insightful? Give me a break. Ditto for this troll's other posts.
Microsoft up to its usual tricks.
When all you have is a hammer, every problem starts to look like a thumb.
You are completely wrong about that. Reflecting your vast Windows experience perhaps?
Library versioning generally takes care of of libc updates. Various daemons have to be restarted to re-open nscd sockets which is a minor blemish, but it usually just works.
When all you have is a hammer, every problem starts to look like a thumb.