Christmas FUD From Microsoft, Smearing "SSH" When the Real Issue is Microsoft Windows
And since Microsoft's software contains back doors, only a fool would allow any part of SSH on Microsoft's environments, which should be presumed compromised.
From a Microsoft-centric (controlled by Microsoft to an extent) site:
What a nice FUD "specimen".
Seems like intentional FUD - or at least misdirection - by Xavier Mertens. We've said for many years SSH does not belong on Windows, where clicking on E-mail attachments may mean "execute". There are so many reasons why a "SECURE" "SHell" (SSH) does not and cannot belong on Windows.
See the following past articles:
- The Real Reason Microsoft Gives Money to OpenBSD is Not Security or Free Software But Proprietary Windows With Back Doors
- Microsoft Wants to Remove (or Deprecate) PuTTY From Windows and Replace It With Proprietary Microsoft Software
- With SSH Keys on Windows the World Will be a Vastly Less Secure Place
- Twisting Severe Holes in Microsoft Windows as an "Open Source" Problem (Darkening Perceptions of SSH Security)
- [Video] How the Media Blamed SSH and Linux (for Nearly a Whole Fortnight!) Instead of Microsoft's GitHub and Systemd
- OpenSSH Must be Taken Very Seriously and Not Left for Microsoft/NSA/GCHQ to Handle
- GNU/Linux is Unsafe Because You Can Choose Password 'GoodMorning123' and Open to Logins From Anywhere on the Planet
Thankfully we already did a lot of "prebunking" of common FUD patterns, so we can more or less rebut by linking to prior FUD and response to it. A lot of the above is "told you so" or "we were right" (to predict what would happen).
"Microsoft and its minions is blaming Windows holes on SSH," an associate has said, "again".
They will carry on doing it, we just need to properly respond in a timely fashion. Sooner or later they'll give up; they don't like being admonished. █