"I don’t want a back door. I want a front door." -- Director of the National Security Agency (NSA), only days ago

WHILE many journalists still refuse to call out Windows (see this new piece from Dan Goodin, who writes about crackers hoarding Windows hosts by the millions -- in botnets -- while mentioning the word "Windows" only once, very deep inside the article), some have no choice by to acknowledge that not every single computer runs Windows and therefore we should call out Windows when it's clearly to blame.

"This wouldn't be the first time it happens; recall how Google had to alert Microsoft for 3 months about a serious flaw while Microsoft did absolutely nothing (as if the intention was to keep Windows insecure, albeit secretly, very much like Apple)."Although there is no "branding" yet (as Microsoft buddies from a a Microsoft-linked firm like to do to Free/libre software bugs), there is a very serious bug in all versions of Windows (even the one still in development) that Microsoft's allies at the NSA must be very happy about, especially as the bug is 18 years old (meaning that Windows has allowed remote access since 1997, or around the time Microsoft was seeking to appease the US government after it had shamelessly broken many laws).

The bug was found not by Microsoft but by this team (press release), which probably has no access to Windows source code. This wouldn't be the first time it happens; recall how Google had to alert Microsoft for 3 months about a serious flaw while Microsoft did absolutely nothing (as if the intention was to keep Windows insecure, albeit secretly, very much like Apple).

ISPs should now restrict or ban Windows use, as it poses a huge risk (botnets and DDOS, never mind risk to all data stored on machines running Windows). Here is some early coverage of this [1, 2], some correctly emphasising that it's a 18-year-old vulnerability [1, 2].

Let's see if this starts a big debate about the insecurity of proprietary software (as other bugs with "branding" did to Free software, by means of gross generalisation). This "New Security Flaw Spans All Versions Of Windows" (similar wording in this headline). 18 years, eh? It even predates 9/11. It's older than some readers of this Web site.

Watch this disgraceful piece titled "Will Microsoft’s Security Measures in Windows 10 Tarnish Open-Source Development?"

Yes, it's more propaganda; The disingenuous openwashing of Windows continues, as we'll show in our next post. ⬆

"Our products just aren't engineered for security."

--Brian Valentine, Microsoft executive