![]() |
![]() |
|
October 21, 2003Ballmer says Linux not accountable for securityAccording to Steve Ballmer, the rivalry between Microsoft Windows and Linux comes down to the basic question of whom customers should trust. There is an article in which Mr. Ballmer says that "There's no roadmap for Linux. Nobody is held accountable for security problems with Linux." I do not see how the open development process of Linux equates to the fact we should blindly trust Microsoft. There is a definitive path for kernel development, just as there is for Windows. And, does this mean we can now hold Microsoft accountable because Steve says we can? If so, I would like to know who to send the bill to for all the overtime InfoSec people are putting in cleaning up the mess of the recent months. Anyways, I don't have enough time in the day to criticize such erroneous thinking. I think Mr. Ballmer needs a tutorial on Crystal Box security vs. Black Box security thinking, and then equate the word "TRUST" accordingly. You should read the article yourself. Ballmar makes the Microsoft position that they should be trusted because they have the infrastructure to properly address security patches. This is the SAME infrastructure that released the ORIGINAL code that had security issues, and the SAME infrastructure that did the "amazing code audit" as part of their Trustworthy Computing Initative. Should we trust this SAME infrastructure? No, I think not. Want to earn my trust Microsoft? How about taking these actions:
Take these steps and I will begin to consider trusting you more openly. P.S. In all fairness, Microsoft IS getting better. But this is the type of thing where "Trust, but Verify" is in order. Blind trust is NOT an option yet. Posted by SilverStr at October 21, 2003 01:45 PM | TrackBackComments
Article linked from /. is at http://www.groklaw.net/article.php?story=20031022014413296 Posted by: Arcterex at October 22, 2003 03:22 PM |
![]() ![]()
My 5 Favorite Books
Writing Secure Code
Secure Programming Cookbook Security Engineering Secure Coding Principles & Practice Inside the Security Mind ![]()
My 5 Favorite Papers
Smashing the Stack
Penetration Studies Covert Channel Analysis of Trusted Systems DoD Trusted Computer System Evaluation Criteria NSA Security Recommendation Guides ![]()
Archives
May 2006
April 2006 March 2006 February 2006 January 2006 December 2005 November 2005 October 2005 September 2005 August 2005 July 2005 June 2005 May 2005 April 2005 March 2005 February 2005 January 2005 December 2004 November 2004 October 2004 September 2004 August 2004 July 2004 June 2004 May 2004 April 2004 March 2004 February 2004 January 2004 December 2003 November 2003 October 2003 September 2003 August 2003 July 2003 June 2003 May 2003 April 2003 March 2003 February 2003 January 2003 December 2002 November 2002 October 2002 September 2002 August 2002 July 2002 ![]() |
|