Bonum Certa Men Certa

Prominent U.S. Government Figure Blames Microsoft for Security Problems, Dell Disagrees After Alleged Microsoft Pressure

Richard Clarke



Summary: The problems associated with Windows are explained by another longtime professional in this area; Dell's reversal regarding GNU/Linux security agitates GNU/Linux users who suspect that Microsoft is at least partly responsible for the change

MR. Richard A. Clarke is no person to be ignored. As Ars Technica recently revealed, Clarke blames Microsoft for many security problems that jeopardise national security and the Huffington Post has just written about this as well:



As Clarke reports, prior to the 1990s, the Pentagon made extensive use of specialized software designed by in-house programmers and a few defense contractors. But under pressure from libertarian ideologues and business lobbyists, the Pentagon began to use commercial software instead -- in particular, Microsoft software. However, it turned out that Microsoft had built a low cost brand based on a principle of "one format for all" -- rather than software that was tailored to special security needs. Problems soon arose, including, as Clarke recounts, a 1997 incident when the USS Yorktown, a Ticonderoga-class cruiser whose ship operations were administered on computers running Windows NT, was rendered inoperable after Windows crashed. "When the Windows system crashed, as Windows often does," Clarke writes, "the cruiser became a floating i-brick, dead in the water." After this and a "legion of other failures of Windows-based systems," the Pentagon considered a shift to free, open-source operating systems like Linux. The code of open-source software can be altered by the user, and so the government would be free to change the software without interference from companies jealously guarding their design. It is also free.

Such a switch, though, would have been disastrous for Microsoft's lucrative dealings with the government. The company was already fiercely opposed to regulation of its products' security; it did not want the added delay and cost of improving its software in order to decrease its vulnerability. If the government switched to open-source software, it could make the improvements itself -- but doing so would deal a major blow to Microsoft's profits. So Microsoft moved to prevent the government from exploring any alternatives. It "went on the warpath," writes Clarke, threatening to "stop cooperating" with the government if it adopted an open-source platform. It made major campaign contributions and hired a small army of lobbyists. Clarke outlines their purpose as: "don't regulate security in the software industry, don't let the Pentagon stop using our software no matter how many security flaws it has, and don't say anything about software production overseas or deals with China." (China, security experts feared, could plant logic bombs and malware into the software.)

Clarke reports that Microsoft insiders admitted that the company "really did not take security seriously," because "there was no real alternative to its software, and they were swimming in money from their profits."


For those who have not noticed, we updated twice each post about the Dell incident (it says "Updatedx2") in order to show the response to what Dell had done [1, 2]. People alleged that Microsoft was responsible for changes in security advice and here is another new example of a rant:

Gosh, I wonder how many lawyers, and how many threats, it took to get that changed, and whose payroll the lawyers were on, and who was making the threats?

I think I'll go over in the corner and hurl now. The whole situation, and the disgusting company behind it all, makes me ill.


We already possess undeniable evidence of Microsoft's retaliation threats against Dell. Microsoft will continue to produce fake security reports, bribe journalists, and harass those who expose Microsoft's security problems. Coercion is what Microsoft does best and if even giants like Dell are so spineless, shouldn't there be room for an investigation? It's an obstruction of truth.

Comments

Recent Techrights' Posts

1989: Free Software as "Open" Software (OSI Didn't Coin "Open Source", It Also Predates Linux)
"One man's fight for Free software"
Linux Journal Might Have Become the Latest Slopfarm Targeting "Linux", the Trends Are Concerning for Dying News Sites
They tarnish the Web with junk and then die
On "Learning to Code"
quality may suffer, plus things get bloated
Quick Points Regarding This Week's Court Hearing
it paves the way for us to squash all the SLAPPs from Microsofters
 
Links 21/06/2025: Data Breach With 16 Billion Passwords, Dutch Government Recommends Children Under 15 Stay off TikTok and Instagram
Links for the day
Gemini Links 21/06/2025: Notes about Typst (and LaTeX) and Opos
Links for the day
Microsoft's Competition Tactics: Sabotage GNU/Linux Installs, Block Chrome
Edge is dying
The Microsoft OOXML Modus Operandi: Throw 1,000 Pages of Other People's Work for a Judge to Read Ahead of a One-Hour Meeting
No time to discuss this - that's the point
Formalities Officers (FOs) at the EPO Are in Trouble, Reveals Internal Report
We already know, based on an HR pattern we saw at IBM and elsewhere, that reallocating roles can be prerequisite for dismissal and those who do so expect many to resign anyway
The Web is Slop and FUD, Let's Go to Gemini Protocol
Lupa sees self-signed capsules at 92.4%
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, June 20, 2025
IRC logs for Friday, June 20, 2025
Links 21/06/2025: Phone Bans for Concerts, Tensions in Taiwan Strait
Links for the day
Gemini Links 21/06/2025: Spoilers, Public Yggdrasil Node, Changes to AuraGem Search
Links for the day
"Six years of Gemini!"
From gemini://geminiprotocol.net
Gemini Links 20/06/2025: Summer Updates and Hardware Failures
Links for the day
Links 20/06/2025: Google Shareholder Sues Google and Google Sued for Defamatory Slop ('Hey Hi') Word Salads ('Summaries')
Links for the day
Common Mistake: Believing Social Control Media Will Document Your Writings/Thoughts and Search Engines Like Google Will Help You Find These
Many news sites wrongly assumed that posting directly to Twitter would be acceptable
The Manchester Bees and This Hot Summer
We have had a fantastic week so far this week
Gemini Protocol Enters Its Seventh Year, Growth Has Accelerated!
Maybe in June 20 2026 there will be over 3,500 active capsules?
Mastodon and the Fediverse Have an Issue: Liability for Content (Even in Other Instances) and Costs
self-hosting is the only logical path forward
Why Microsoft and Its 'Hey Hi' (Slop) Frenzy Fail While Sinking in Deep, Growing Debt
Right now, like Twitter around the time it was sold to MElon, "open" "hey hi" is a big pile of debt with a lot to pay for that debt (interest payments)
Europe is Leaving Microsoft, the Press Coverage Isn't Sufficiently Helpful
The news is generally positive, but the press coverage leaves so much to be desired
Slopwatch: Linuxsecurity, BetaNews, and Linux Journal
slippery slope
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, June 19, 2025
IRC logs for Thursday, June 19, 2025
Gemini Links 20/06/2025: Gemini Protocol Turns 6!
Links for the day
Links 19/06/2025: Ghostwriting Scam and Fentanylware (TikTok) Buying Time
Links for the day
Microsoft's Windows is a Niche Operating System in Africa
African nations aren't a large contributor to Microsoft's income, but if many African nations move away from Windows, then the monopoly is at risk
Gemini Links 19/06/2025: Unix Primitivism, Zine Club, and Gemini Protocol Turns 6 at Midnight
Links for the day
Links 19/06/2025: WhatsApp Identified as Assassination 'Crosshairs', Patreon Now Rips Off People Even More
Links for the day
"Told You So": Another Very Large Wave of Microsoft Layoffs Now Confirmed in Mainstream Media
So we were right to believe the rumours, based on the credibility of prior such rumours
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, June 18, 2025
IRC logs for Wednesday, June 18, 2025