LinuxWorld
Subscribe to this site with RSS

Another black eye for 'Trustworthy Computing'

Recent news reports have posited that 50% of all e-mail is spam. Given what I've encountered, that number doesn't seem ridiculously high. It made me wonder about another number. When the "worms of August" arrived, I wonder what percentage of the Internet's bandwidth was consumed downloading service packs and "critical fixes" from Microsoft?

I doubt that we'll ever find out. Unlike most sites, which brag about their visitors and the number of downloads, Microsoft's support site is mum on the subject. All in all, the Blaster and follow-on worms gave "Trustworthy Computing" a big, black eye.

Given the fact that Windows Server 2003 - supposedly the first product really to benefit from Microsoft's efforts - was the hardest hit of all, one really has to wonder about Microsoft's plan.

Ironically, around the time of the infestation, I was plowing through a popular third-party book on Win 2003. It referenced the Microsoft initiative and made broad (but unsubstantiated) references to how Microsoft's development team combed through every line of the code.

It went further to talk about how this new code could detect problems in real time and heal itself - well obviously not with this problem.

For us, Win 2003 constituted the biggest problem. Even after the first round of patches was applied and the various worm scanners were run, it just kept bouncing up and down like a yo-yo. Our pre-release version was not even "fixable" - and we had to wipe it out and restart.

For the other machines in the organization, it was "scan and patch."

Might I have avoided my problems by having everyone "current"? Perhaps, but I've got some issues with taking that approach.

For starters, nobody puts a gun to Microsoft's head to say that the company must release an operating system at a particular time. It picks the time (although delays might affect the vendor's stock price). It is a big enough job to move, say, from Win 2000 to Windows XP or Win 2003, so once completed, one is hoping for some level of stability.

React: Give us your thoughts on the issues here.
Use this form to start a public discussion with other Linux World users on this article.
Log In | Register for an account (Why you should)

Note: Register to have your user name appear; otherwise your comment will show up as "Anonymous."

*Anonymous comments will only appear once they are approved by the moderator.

Featured Whitepapers
Newsletter sign-up

Sign up for one of Network World's newsletters compliments of Linux World

Linux & Open Source News Alert
Web Applications Alert
Video & Podcast Alert
Security: Threat  Alert
Virtualization Alert

Email Address: