Linked by Thom Holwerda on Wed 15th Apr 2009 09:54 UTC
Permalink for comment 358633
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2005-08-29
If you can blame "Microsoft" for the Conficker worm, then who do you blame when it comes to a Linux distribution?
First, here's why I blame Microsoft:
The vulnerability was in the RPC server service. This is a service that's completely unneeded for 99% of computers running windows. Why is it enabled by default? That's retarded.
If the default was off, then conficker would barely be a blip on the internet radar especially since computers that actually use the server service are usually administers by semi-competent admins--not home users that have never installed a security update.
So, what if this were a linux vulnerability?
I don't know. For a long time now, the default settings for almost any linux distribution is to not have anything listening on the network (except ssh, which they *should* change... enabling ssh if you need it isn't that hard).