, 2004-08-11
Service Pack 2 for XP represents a sea change in Microsoft's security posture. Here's why you should ignore the naysayers and start planning your upgrade.
Expand all |
Post comment
Redmond's Salvation? What?
2004-08-11
Dave (2 replies)
Dave (2 replies)
Redmond's Salvation
2004-08-11
Anonymous (1 replies)
Anonymous (1 replies)
Redmond's Salvation
2004-08-12
Anonymous (1 replies)
Anonymous (1 replies)
Redmond's Salvation
2004-08-13
Rob Hughes (1 replies)
Rob Hughes (1 replies)
Redmond's Salvation
2004-08-11
Anonymous (2 replies)
Anonymous (2 replies)
A better idea
2004-08-12
Aenox (1 replies)
Aenox (1 replies)
Big Improvements..... yeah right
2004-08-12
Bug Me Not <sf@dodgeit.com> (1 replies)
Bug Me Not <sf@dodgeit.com> (1 replies)
Redmond's Salvation
2004-08-12
Anonymous (1 replies)
Anonymous (1 replies)

Also, when you said:
"In an earlier column I identified old software as a contributing factor to security issues, prompting a flood of "Who the hell do you think you are telling me I have to upgrade?" e-mails. Well, I'm someone who cares about computer security. I'm not telling anyone they "have" to upgrade, but I will say that if you make the choice (or your company does for you) to maintain older, less secure software when you know something far better is out there, then you must take responsibility for your security posture. "
...err, here I have a bone to pick. I thought Microsoft was busily denying that they were forcing customers onto an upgrade treadmill. What you just said tends to belie that claim... coercion is just as bad as assertion, after all.
Also, for many companies it is more of a hardware cost issue in keeping to Win2k and WinNT, than it is a software issue (though software does play a rather large role as well when it comes to in-house custom apps... )
Ugh. Either way it stinks, and MSFT of all people should be careful of this; it may force CIO/CTO's to start looking elsewhere for their desktop and security (at least on the perimeter) needs.
/P
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/columns/259/27918#27918