Linux Today: Linux News On Internet Time.
Search Linux Today
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

JustTechJobs.com

LinuxToday Newsletters
Server Daily
IT Management Daily
Subscribe News
Subscribe PR
Subscribe Security

internet.com
Internet News
Small Business

Advertise
Newsletters
Tech Jobs
E-mail Offers

 










Current Newswire:

A Selection of the Very Best Open Source Tutorials and Tools

Android Ice Cream Sandwich ported to x86 tablets, netbooks and notebooks

SECURITY: Google Chrome 17 Improves Security

How to read a CSV file in Perl?

Red Hat Brings Gluster to Amazon Cloud

New Linux kernel fixes power-saving issues

Using Wii remote with Android Device- Taking Gaming to the Next Level

Commercial Support now available for the open-source NGINX Web server

Linux Top 5: Linux's New Fellow

RebeccaBlackOS - First Live CD Running Wayland Display Server



Applications Management Engineer Sr (NYC)
Next Step Systems
US-NY-New York

Justtechjobs.com Post A Job | Post A Resume
:Who's really to blame for the Windows XP Patch BSOD?
Who's really to blame for the Windows XP Patch BSOD?
Feb 19, 2010, 20 :33 UTC (2 Talkback[s]) (5206 reads)

(Other stories by Steven J. Vaughan-Nichols)

[ Thanks to Steven J. Vaughan-Nichols for this link. ]

"More than a week after Microsoft released an XP patch that seemed to cause BSODs (Blue Screen of Death), Microsoft announced that the immediate cause was the Alureon rootkit. Fair enough, but what about the 17-year old Windows security hole that the rootkit was exploiting?

"I mean, come on. This bug dates back to 1993 when Windows for Workgroups 3.11 and Windows NT 3.1 instead of Windows 7 were the hot new versions of Windows. Many of you have never even seen those operating systems much less used them. Since Microsoft has left this security hole open almost long enough for it to be old enough to vote, shouldn't they get some of the blame?

"After all, the hackers behind Alureon, aka TDSS, Tidserv and TDL3, botnet were able to fix their malware to work around the Windows' fix before Microsoft finally figured it out. Maybe Microsoft should hire them to work on Windows security instead of relying on their own in-house software engineers. Nah. They're probably making more money from their botnets than Microsoft is willing to pay them."

Complete Story

Related Stories:
32% of computers with AV protection are infected(Feb 11, 2010)
New Russian botnet tries to kill rival (Feb 10, 2010)
Russia, Brazil Lead Cyber Attack Barrage(Jan 20, 2010)
New Malware Tactics, Targets Expected in 2010(Dec 31, 2009)
Attackers Buying Own Data Centers for Botnets, Spam(Dec 22, 2009)
New Trojan virus poses online banking threat(Sep 21, 2009)
Defying Experts, Rogue Computer Code Still Lurks(Aug 27, 2009)
Why Windows security is awful(Aug 25, 2009)


Index Mode   |   Flat Mode   |   Thread Mode   |   Thread Flat  
  Talkback(s) Name  and Date
It is a known issue that enterprises usi ...   Patching Windows.   
Khan Md Ashraf
Feb 21, 2010, 02:07:18
 
Actually that applies to any OS, the uni ...   Re: Patching Windows.   
Jim
Feb 21, 2010, 02:25:19
 
  Home | Search Talkbacks | Customize View    Top of Page  



Enter your comments below:

* Your Name:

* Your Email Address:

* Subject:

CC: [will also send this talkback to an E-Mail address]

* Comments:

Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content.

Fields marked with * are required!

..............................




All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP