EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

07.01.20

Corporate Media Blames ‘China’ and ‘Open Source’ for Back Doors in Microsoft’s Intentionally Flawed Proprietary Software That’s Causing Chaos

Posted in Asia, Australia, Deception, FUD, Microsoft, Security, Windows at 11:16 am by Dr. Roy Schestowitz

Corporate media has long helped Microsoft distract the public, oftentimes leveraging nationalism to achieve this

The red flags

Summary: ‘Red Scare’ tactics are being used to divert attention away from Microsoft’s incompetence and conspiracy with the NSA (to put back doors in everything, essentially making all software inherently vulnerable, by design)

LAST month we published our hospital series. It was about hospital managers and media, in cohesion, blaming or punishing Microsoft’s competition for Microsoft’s own failings. Hospitals are being taken out of service because of Microsoft and somehow, perhaps miraculously, everything gets blamed except Microsoft. It’s part of a media cover-up and hospital blame-shifting pattern.

“It’s almost as though someone is in deep denial about the nature of the real culprit, instead blaming people who exploit the holes (as they can).”It’s barely surprising to hear — as I did earlier this week — that: “An analysis of the ongoing massive cyber attack on Australia finds mostly Microsoft vulnerabilities exploits.”

The official page speaks of “tools copied almost identically from open source.”

They focus on how the exploits were put together, not the holes that they exploit. But this part is telling: “During investigations, a common issue that reduced the effectiveness and speed of investigative efforts was the lack of comprehensive and historical logging information across a number of areas including web server request logs, Windows event logs and internet proxy logs. The ACSC strongly recommends reviewing and implementing the ACSC guidance on Windows Event Logging and Forwarding and System Monitoring.”

This part is pretty clear about Windows being the issue. “Stop public spending on Microsoft,” the person who highlighted to to me said. “Public Money, Public Code. Media blames China.” The above page also link to this page: “The actor has been identified leveraging a number of initial access vectors, with the most prevalent being the exploitation of public-facing infrastructure — primarily through the use of remote code execution vulnerabilities in unpatched versions of Telerik UI. Other vulnerabilities in public-facing infrastructure leveraged by the actor include exploitation of a deserialisation vulnerability in Microsoft Internet Information Services (IIS), a 2019 SharePoint vulnerability and the 2019 Citrix vulnerability.”

IIS, SharePoint, Citrix…

It’s almost as though someone is in deep denial about the nature of the real culprit, instead blaming people who exploit the holes (as they can). Not the people are blamed but the tools. Or sometimes the people, especially if they “foreigners”…

Another person highlighted to us this new piece which he says demonstrates “Windows TCO,” albeit it is “Microsoft marketeering spam” because it sort of rewrites the history of Maersk incidents, which years ago the media said had a major catastrophe due to Windows. This page entitled “Maersk, me & notPetya” says: “Within a couple of hours, it was clear this had impacted every single domain-joined Windows laptop, desktop, virtual machine and physical server around the planet.”

So Windows, with its notorious NSA back doors (for which there are remote access tools — tools which leaked online), is the actual culprit. Maybe stop using something which you know to be flawed (and often by design)?

06.26.20

Adapting to Microsoft

Posted in GNU/Linux, Microsoft, Security, Windows at 10:03 pm by Dr. Roy Schestowitz

Response to “Adapting To Circumstances” from Planet Ubuntu (hours ago)

PuTTY
Handing the keys over the Microsoft, even literally

Summary: Doing ‘Linux’ the way Microsoft wants you to do it is merely strengthening the Microsoft monopoly; even Planet Ubuntu is currently promoting this inane approach

IT’S not often that we do line-by-line rebuttals anymore, but this one merits a rebuttal. It’s a symptom of concessionary thinking, which is basically accepting Microsoft’s supremacy over GNU/Linux and Free software in the name of “compromise” or “convenience”. It’s why we end up with everything in a Microsoft monopoly called GitHub and lots of OEMs paying Microsoft for “Linux” because of software patents (which are likely bunk anyway).

“It’s a symptom of concessionary thinking, which is basically accepting Microsoft’s supremacy over GNU/Linux and Free software in the name of “compromise” or “convenience”.”Below we quote the original, with a response following every statement, hopefully putting things in context:

I have written prior that I wound up getting a new laptop.

OK, lots available or around these days with GNU/Linux pre-installed. More so over time.

Due to the terms of getting the laptop I ended up paying not just for a license for Windows 10 Professional but also for Microsoft Office.

So what? Proprietary software is worse than worthless. What’s the actual value of Office? It’s mere rental of a piece of malware. Money down the drain.

As you might imagine I am not about to burn that much money at the moment.

You already have. You paid for Windows and for an Office licence.

With the advent of the Windows Subsystem for Linux I am trying to work through using it to handle my Linux needs at the moment.

WSL is Windows, not Linux. WSL doesn’t even have Linux in it. It’s a misnomer. As for WSL2, only about 150,000 people use it worldwide. It’s a failure.

Besides, I did not realize OpenSSH was available as an optional feature for Windows 10 as well.

May I introduce you to PuTTY? It has been around for… how long? Two decades? PuTTY was not controlled by Microsoft, so Microsoft had to ‘reinvent’ it… to keep people like you in the gated community [sic] (prison) of Windows.

That makes handling the herd of Raspberry Pi boards a bit easier. Having the WSL2 window open doing one thing and a PowerShell window open running OpenSSH makes life simple. PowerShell running OpenSSH is a bit easier to use compared to PuTTY so far.

So now you’re running Microsoft’s patented and non-standard shell. Hurray to freedom! Just don’t write any programs/scripts in it. That’s Microsoft lock-in right there.

Did you supply private keys? Oh, wait till you find out Microsoft hoovers all the data from Windows and works closely with the NSA and others… so you might as well assume your keys are already compromised.

The Ubuntu Wiki mentions that you can run graphical applications using Windows Subsystem for Linux. The directions appear to work for most people. On my laptop, though, they most certainly did not work.

So Ubuntu wastes space and time promoting Microsoft’s monopoly and an attack on GNU/Linux. The fact that the documentation did not work for you means that Microsoft is getting its way. It’s already painful enough, giving GNU/Linux a bad name.

“Hey, why bother with this Linux thing? Might as well stay with Windows…”

After review the directions were based on discussion in a bug on Github where somebody came up with a clever regex.

Oh, GitHub. Lovely! So now we’re turning to Microsoft for ‘Linux’ bug reporting.

The problem is that kludge only works if your machine acts as its own nameserver. When I followed the instructions as written my WSL2 installation of 20.04 dutifully tried to open an X11 session on the machine where I said the display was.

At this stage you could have instead asked yourself, “why did I not just wipe Windows and why bother with this whole “kludge” (your word)?”

Unfortunately that regex took a look at what it found on my machine and said that the display happened to be on my ISP’s nameserver. X11 is a network protocol where you can run a program on one computer and have it paint the screen on another computer though that’s not really a contemporary usage. Thin clients like actual physical X Terminals from a company like Wyse would fit that paradigm, though.

Wow, talk about reinventing the wheel. Microsoft taking back technology two decades. I literally did that in 2001. A lot. Without issues. Even Cygwin could handle that very reliably at the time.

After a wee bit of frustration where I was initially not seeing the problem I had found it there. Considering how strangely my ISP has been acting lately I most certainly do not want to try to run my own nameserver locally. Weirdness by my ISP is a matter for separate discussion, alas.

I inserted the following into my .bashrc to get the X server working:

export DISPLAY=$(landscape-sysinfo –sysinfo-plugins=Network | grep IPv4 | perl -pe ‘s/ IPv4 address for wifi0: //’):0

Considering that my laptop normally connects to the Internet via Wi-Fi I used the same landscape tool that the message of the day updater uses to grab what my IP happens to be. Getting my IPv4 address is sufficient for now. With usage of grep and a Perl one-liner I get my address in a usable form to point my X server the right way.

Congrats on reinventing X forwarding?

Elegant? Not really. Does it get the job done? Yes. I recognize that it will need adjusting but I will cross that bridge when I approach it.

Since the original bug thread on Github is a bit buried the best thing I can do is to share this and to mention the page being on the wiki at https://wiki.ubuntu.com/WSL. WSL2 will be growing and evolving. I suspect this minor matter of graphical applications will be part of that evolution.

So basically, here you are dealing with issues long solved (like two decades ago). And all this? Just so that you can run Windows while pretending to use GNU/Linux. And it has a keylogger, too. According to the latest press reports, Microsoft also ‘steals’ data from Firefox users on Windows. So good luck; assume Microsoft does the same to your ‘Linux’ setup.

So well done, Canonical. There are now 150,001 WSL2 users. And your documentation sucks. Maybe restart the focus on bug #1 and try replacing Windows instead of ‘improving’ it, driving more Ubuntu members (like the above) back to Windows.

06.14.20

Linux Foundation Pretends Security ‘Best Practices’ is Outsourcing to Microsoft. All ‘Gold Badges’ (All of Them Except Linux) Go to Projects That Are Microsoft-Controlled at GitHub, With NSA PRISM.

Posted in Free/Libre Software, Kernel, Security at 3:19 am by Dr. Roy Schestowitz

‘Gold Badges’ sponsored by Microsoft

A tuxedo Pooh: Free software project with CII badge; When you realise 'gold level best practices' means Microsoft-controlled

Summary: The Linux Foundation and others boast about being among those half a dozen projects honoured with a “CII” (not software patents) badge; the main issue is, except for Linux (the kernel) everything was outsourced to Microsoft’s proprietary software monopoly (GitHub), which is also a sponsor of “CII”

06.09.20

Index of the Series About Windows Inside Hospitals (Causing Hospitals to Become Disaster Zones)

Posted in Microsoft, Security, Windows at 6:39 pm by Dr. Roy Schestowitz

Two different Phantoms: [W]hen nobody is using Windows, there will be no botnets -Professor Eben Moglen, 2010

Summary: Now that the 16-part series is finished, with no further whistleblowers coming forth, we conclude with the index below

  1. Microsoft Kills: An Introduction
  2. Microsoft Killed Far More Patients Than COVID-19 Killed
  3. Microsoft Kills: Hospitals Taken Over by Windows Crackers and Hospital Staff Threatened Not to Talk About It
  4. Very Bad Reporting or Deliberately Shallow Media Coverage After Microsoft Windows Hands Hospitals Over to Crackers
  5. Microsoft Cult-Like Tactics Destroy Hospitals by Ripping Apart Everything Microsoft (and the NSA) Cannot Control
  6. Stories From the Battleground (Hospitals Where Windows Killed More Patients Than COVID-19 Has Killed)
  7. Nothing to See Here, People, Please Move Along. The “System is Down…”
  8. With Microsoft Windows on Key Systems Many Hospitals Become Remotely Controlled and Nonoperational
  9. The Difficulty of Blowing the Whistle on Hospitals Brought Down by Microsoft Windows
  10. When the Response to Hospitals Being Systematically Cracked Through Microsoft Products Like Windows is… Blocking the Competition of Microsoft
  11. Trust Microsoft With Everything Including Your Life
  12. Removing Free/Libre Software as an Inadequate Response to Microsoft Windows (With Back Doors) Getting Compromised, Killing People
  13. Hostility and Aggression Towards Staff That Does Not Use Windows After Windows Takes Entire Hospital Down
  14. Allegations That Microsoft Will Ruin Besieged Clinics and Hospitals to Retaliate Against Those Who Name the Culprit
  15. Never Mind If GNU/Linux Works Better Inside Hospitals and Free Software Not Only Safer But Vastly More Efficient…
  16. Windows Ransomware Must Not be Unspeakable When People Die in Large Numbers Due to That (and Windows Has Intentional Back Doors)

06.07.20

A Couple of Quick Points About Hackers…

Posted in Free/Libre Software, Security at 3:26 pm by Guest Editorial Team

Article by figosdev

Screen on Internet

Summary: “First — before it even comes up — I recently talked about Richard Stallman’s website being “hacked” — we don’t know exactly what happened there, but nobody was trying to imply that outsiders had anything to do with it.”

Since I’ve raised the ire of someone apparently associated with DEF CON on Twitter, I thought I’d clarify a couple things I hoped were clear already:

First — before it even comes up — I recently talked about Richard Stallman’s website being “hacked” — we don’t know exactly what happened there, but nobody was trying to imply that outsiders had anything to do with it.

Personally, I think it was someone who already had access (so “hacked” was a casually-chosen and technically inaccurate word). I never mentioned “hackers” there, but I don’t believe there was a compromise of security of any kind (perhaps there was, but it’s not what I actually suspect happened).

I wouldn’t even bother clarifying that, if I hadn’t just read a tweet from someone apparently associated with DEF CON. At first I was confused by this (what did they think I said about hackers?) but many hours later, I went looking for the actual quote and figured out what they read.

Second, and probably more importantly, I didn’t “blame hackers” for what has happened to the GNU project. That was a simple misreading of the line I wrote. What I said (you can read the full article here) is that rms built a house “for all hackers” (his definition of the word) and this is the part people are obviously misreading:

“What I dispute is that you have any right whatsoever, after helping rms build a house for all hackers…

(Yes, God Damn You, ALL hackers — just because you want to be the thought police and say he doesn’t kowtow to people exactly the way you want, doesn’t change the fact that he HAS IN FACT welcomed people”

The emphasis here is on (Stallman welcoming) “ALL” hackers, and the “Damn You” part was directed at people who argued he was not welcoming to certain groups (of hackers).

I realise that anybody can take offense to his personality and feel unwelcome, though I side with those who have come from each group and defended him, pointing out the ways in which he not only treated them as anybody else, but encouraged them to be “hackers” for the GNU project.

So no — I did not blame “hackers” for the fall of the GNU project. I blamed a handful of GNU maintainers, but this line was completely misread. I was saying that GNU was a house rms built for ALL hackers (people from every group of people, regardless of gender, sexual orientation, religious beliefs, etc.)

I hope this helps put the statement back in the context it was intended in.

“GNU is Open Source” (where I mention Richard Stallman’s website) could easily be my last story for Techrights for quite a while at least. Over time I’ve said what I want to say, I’ve offered everything I can think of in terms of solutions.

I’ve said what I think of the present, near future, and more distant future. Only the more distant future gives me much hope for Free Software. I do recommend people continue to fight for freedom, if only so their political muscles don’t atrophy. I don’t know if there’s anything else to say about Free Software. But if there is, it will probably have to be someone else who writes it.

Long live rms, and (as I’ve said several times in stories for Techrights…) Happy Hacking.

Licence: Creative Commons CC0 1.0 (public domain)

05.31.20

Windows Ransomware Must Not be Unspeakable When People Die in Large Numbers Due to That (and Windows Has Intentional Back Doors)

Posted in Microsoft, Security, Windows at 4:38 am by Dr. Roy Schestowitz

“Winner also suggested they would “mysteriously lose the form,” and as it turns out, that is essentially the bureaucratic game they are playing with her life as the coronavirus remains a risk in prisons throughout the United States.”The Dissenter 2 days ago (shades of Seattle PD)

Previously in this series:

  1. Microsoft Kills: An Introduction
  2. Microsoft Killed Far More Patients Than COVID-19 Killed
  3. Microsoft Kills: Hospitals Taken Over by Windows Crackers and Hospital Staff Threatened Not to Talk About It
  4. Very Bad Reporting or Deliberately Shallow Media Coverage After Microsoft Windows Hands Hospitals Over to Crackers
  5. Microsoft Cult-Like Tactics Destroy Hospitals by Ripping Apart Everything Microsoft (and the NSA) Cannot Control
  6. Stories From the Battleground (Hospitals Where Windows Killed More Patients Than COVID-19 Has Killed)
  7. Nothing to See Here, People, Please Move Along. The “System is Down…”
  8. With Microsoft Windows on Key Systems Many Hospitals Become Remotely Controlled and Nonoperational
  9. The Difficulty of Blowing the Whistle on Hospitals Brought Down by Microsoft Windows
  10. When the Response to Hospitals Being Systematically Cracked Through Microsoft Products Like Windows is… Blocking the Competition of Microsoft
  11. Trust Microsoft With Everything Including Your Life
  12. Removing Free/Libre Software as an Inadequate Response to Microsoft Windows (With Back Doors) Getting Compromised, Killing People
  13. Hostility and Aggression Towards Staff That Does Not Use Windows After Windows Takes Entire Hospital Down
  14. Allegations That Microsoft Will Ruin Besieged Clinics and Hospitals to Retaliate Against Those Who Name the Culprit
  15. Never Mind If GNU/Linux Works Better Inside Hospitals and Free Software Not Only Safer But Vastly More Efficient…

Flight logbook
Sorry, mate… we’ve lost all your records. No backups. No paper.

Summary: Loss of electronic patient records, ransom and downtime among the severe consequences of deploying Microsoft inside hospitals; yet the media rarely names the real culprit (manslaughter charges theoretically possible) and nobody gets punished except those who offer real solutions

THIS is the closing part of the series above, which included some additional memes and humour ‘in between’…

We’d like to think that many people out there can learn something from the experience of our sources (there were several, we’d rather not enumerate them as that number increases risk). The stories have proof associated with them. This is a real issue, a very legitimate problem. It seems to be widespread, not only in the medical domain.

“We’d like to think that many people out there can learn something from the experience of our sources (there were several, we’d rather not enumerate them as that number increases risk).”“I’m paranoid about the “security” people my doctor has hired in the wake of the ransomware attack,” a source once told us.

“I’m afraid that they have already slandered me.”

People in the workplace can sometimes be ranked based on their obedience to some dubious status quo (conformity) or some external corporate interests. It’s universally true that proprietary software vendors dislike technical workers who put the workplaces in control of its own systems rather than some outside ‘cloud’ or contractors. We saw that in Munich.

“People in the workplace can sometimes be ranked based on their obedience to some dubious status quo (conformity) or some external corporate interests.”“My wonderful, free software-friendly IT person was run off [...] and the circumstances were fishy to say the least,” a source explained to us. “Any hope of real control of the network and computer systems was lost at that point.”

Then crackers took over the Microsoft systems, costing lives. But Windows wasn’t being named; instead there were sanctions against anything but Windows and the country’s special agents got involved. What a catastrophe. The media (or “mainstream”) casually talks about COVID-19 death tolls, but never about Windows death tolls. Microsoft prefers it that way and Bill Gates profits from it.

05.30.20

Never Mind If GNU/Linux Works Better Inside Hospitals and Free Software Not Only Safer But Vastly More Efficient…

Posted in GNU/Linux, Microsoft, Security, Windows at 7:10 am by Dr. Roy Schestowitz

Previously in this series:

  1. Microsoft Kills: An Introduction
  2. Microsoft Killed Far More Patients Than COVID-19 Killed
  3. Microsoft Kills: Hospitals Taken Over by Windows Crackers and Hospital Staff Threatened Not to Talk About It
  4. Very Bad Reporting or Deliberately Shallow Media Coverage After Microsoft Windows Hands Hospitals Over to Crackers
  5. Microsoft Cult-Like Tactics Destroy Hospitals by Ripping Apart Everything Microsoft (and the NSA) Cannot Control
  6. Stories From the Battleground (Hospitals Where Windows Killed More Patients Than COVID-19 Has Killed)
  7. Nothing to See Here, People, Please Move Along. The “System is Down…”
  8. With Microsoft Windows on Key Systems Many Hospitals Become Remotely Controlled and Nonoperational
  9. The Difficulty of Blowing the Whistle on Hospitals Brought Down by Microsoft Windows
  10. When the Response to Hospitals Being Systematically Cracked Through Microsoft Products Like Windows is… Blocking the Competition of Microsoft
  11. Trust Microsoft With Everything Including Your Life
  12. Removing Free/Libre Software as an Inadequate Response to Microsoft Windows (With Back Doors) Getting Compromised, Killing People
  13. Hostility and Aggression Towards Staff That Does Not Use Windows After Windows Takes Entire Hospital Down
  14. Allegations That Microsoft Will Ruin Besieged Clinics and Hospitals to Retaliate Against Those Who Name the Culprit

Men at hospital

Summary: With lives on the line one might expect hospitals to choose what’s most secure and generally works best; but in practice there seems to be a leaning towards what bribes best

AS part of my job I keep machines patched and fully up to date in medical research environments. There are no back doors. If there are any, go ahead and show them. GNU/Linux has the full source code publicly available…

I am, however, familiar with the experience of clueless managers at work and outside work. What sources of ours describe is a very common problem. They’re not alone. The technical matters aren’t the sole factor at hand/play; Especially when Microsoft employees and partners offer kickbacks (bribes), take people out for lunch/dinner, and make promises/offers we can’t quite find out about…

“So, just to recap, a hospital got cracked because of Windows and instead of banning Microsoft they decided to ban everything but Microsoft.”Microsoft is like a cult and it turns technical matters into ‘politics’… then they have the audacity to accuse Free software of being a political stunt.

“This was a shock to me,” a source once told him after a GNU/Linux machine had been banned (not confiscated), thereafter prevented from entering the workplace. And when? After a Windows incident — not a GNU/Linux incident — caused a massive security breach. Shouldn’t Windows be banned? Nope. Not when it’s down to Microsoft politics. “I’m a scientist working for a scientist,” the source told us. “The closed-minded bigotry demonstrated was mind-blowing. I’ve met clueless management before, and my boss has shown some of it before, but this latest outburst was amazingly bad.”

So, just to recap, a hospital got cracked because of Windows and instead of banning Microsoft they decided to ban everything but Microsoft.

“So after a massive security breach already killed some patients (this is inevitable) staff that has long relied on a GNU/Linux workflow is being slowed down even further, limiting the capacity to treat patients.”Amazing, isn’t it?

Gotta be seen (to believe it). We saw enough evidence…

“Losing my [GNU/Linux] [redacted] at work makes me look bad,” the source told us. “It takes me three times as long to do anything and my note-taking has fallen back to scribbles on the back of a paper patient schedule. Staff and the doctors still expect me to use my magical [redacted] hacker skills to do things like copy disks for them and to be able to display [redacted] files on disks with missing or defective readers, but I have to pull the magic out of a hiding place and they wonder why I can’t do the same with Windows like they imagine everyone else does.”

So after a massive security breach already killed some patients (this is inevitable) staff that has long relied on a GNU/Linux workflow is being slowed down even further, limiting the capacity to treat patients. And all this because of a Windows incident…

“Why are the alternatives to the “Microsoft way” being banned after the “Microsoft way” caused the loss of lives?”“What’s worse is that I’m forced to advocate shit I hate,” the source continued. “I can’t, of course, tell people what I think because that would be undermining my boss while he’s in a weak position and none of them have a clue to begin with. The contract depends on making the utterly [redacted] Medical Systems electronic records work using really backward techniques like pasting screenshots of pdfs into Word Documents. I had worked out a nice way of making reports with LibreOffice, pdf prints from the [redacted] software, and [redacted], that load quickly but my boss insisted I use the [redacted] raster image methods because Word pulls from the [redacted] database. Word documents take seconds to load and this will greatly annoy the doctor who is expected to click open each for approval. I have to hide my methods from the doctor and tell him that better documents are on the way. I’m his [redacted] on site, so I have to push all of this shit.”

The anger is very much evident from the use of expletives. Imagine being forced to not use something that works a lot better and a lot more securely after that inferior method was in fact the cause of a deadly breach. Why are the alternatives to the “Microsoft way” being banned after the “Microsoft way” caused the loss of lives? Well, we suppose it’s all down to the the “Microsoft way” politics…

The next part of the series will look at additional aspects and conclude. The above-mentioned patterns may be familiar to many; this isn’t a unique case, not an isolated story, so it needs to be told and shared widely.

05.28.20

Allegations That Microsoft Will Ruin Besieged Clinics and Hospitals to Retaliate Against Those Who Name the Culprit

Posted in Microsoft, Security, Windows at 12:48 am by Dr. Roy Schestowitz

Previously in this series:

  1. Microsoft Kills: An Introduction
  2. Microsoft Killed Far More Patients Than COVID-19 Killed
  3. Microsoft Kills: Hospitals Taken Over by Windows Crackers and Hospital Staff Threatened Not to Talk About It
  4. Very Bad Reporting or Deliberately Shallow Media Coverage After Microsoft Windows Hands Hospitals Over to Crackers
  5. Microsoft Cult-Like Tactics Destroy Hospitals by Ripping Apart Everything Microsoft (and the NSA) Cannot Control
  6. Stories From the Battleground (Hospitals Where Windows Killed More Patients Than COVID-19 Has Killed)
  7. Nothing to See Here, People, Please Move Along. The “System is Down…”
  8. With Microsoft Windows on Key Systems Many Hospitals Become Remotely Controlled and Nonoperational
  9. The Difficulty of Blowing the Whistle on Hospitals Brought Down by Microsoft Windows
  10. When the Response to Hospitals Being Systematically Cracked Through Microsoft Products Like Windows is… Blocking the Competition of Microsoft
  11. Trust Microsoft With Everything Including Your Life
  12. Removing Free/Libre Software as an Inadequate Response to Microsoft Windows (With Back Doors) Getting Compromised, Killing People
  13. Hostility and Aggression Towards Staff That Does Not Use Windows After Windows Takes Entire Hospital Down

Leg x-ray

Summary: With a broader picture coming into view, as per the above index, we’re starting to wrap up the series while issuing a call for more stories and eyewitness testimonies, exposing the nature of attacks on hospitals (those almost always target Microsoft and others’ proprietary software, which is technically unfit for purpose)

AS we approach the end of this series we’d like to issue a call for more sources, informants, whistleblowers and so on. We know that some people reading the series have come across similar types of people and encountered similar scenarios. We’d like to hear and tell your story. In exchange we can provide confidentiality and protection. We’ve never (in almost 14 years) compromised a source, either willingly or unwittingly, accidentally. We’re very cautious and patient.

Vitals MonitorIn the more recent parts we talked about lack of access to medical records, which necessarily means bad treatment or lack of treatment. The past couple of parts spoke about retribution from Microsoft and its de facto agents, who believe that nothing except Microsoft can ever work reliably for anything. These are the sorts of people who put Microsoft in everything from the back end to the front end, then looking to misplace blame (covering up their own incompetence) when things go crazy (like crackers in another country grinding things to a halt and demanding ransom).

To make matters even worse the Microsoft boosters then pushed to get rid of backups in the form of paper records. “The root of the problem,” one person told us, “is that my boss told the doctors that there should be no problem treating [redacted] patients a day because he’s able to do more at his larger hospital. They ramped up the patient load and it has been miserable for everyone involved. While that was going on, he pushed to get rid of paper records. This was met with all sorts of resistance and resentment by the staff who did not want to be told what to do by some off-site guru.”

“…these are some of the many ways Microsoft responds to criticisms, pushing back the perfectly reasonable allegations that Windows quite likely caused more deaths (also of young people) than COVID-19 ever did.”One interesting aspect to (and of) this investigation is that it apparently led to attempts to embarrass those who had spoken out, blaming Windows and Windows for the most part, based on technical interpretation of the resultant scenario.

“This might explain some of my doctor’s recent hostility towards myself and some of my boss’s anger,” the person noted. “You would think that my prior warnings about Microsoft insecurity would make me look good when that insecurity shut down most of the hospital for weeks, but the opposite has happened.”

The manipulatorSeparately we learned about media-directed efforts to shame hospitals if they dared name the real culprit (not themselves).

Thankfully, much remains to be told and shown. “Had I managed to finish the ransomware story I was working on,” we were told, “it would have been splashed on my doctor’s desk and I’d probably be fired right now. That’s how bad I think things have gotten here. I’ll be free to publish when they fire me or I find another job. I’ve journaled this and can pull it back out.”

At the moment, for source protection purposes, we’ve not named any places, people, companies or other potentially identifying details. But the scenarios described in this series are very much real. And we hope readers can familiarise themselves with patterns and themes; these are some of the many ways Microsoft responds to criticisms, pushing back the perfectly reasonable allegations that Windows quite likely caused more deaths (also of young people) than COVID-19 ever did.

« Previous entries Next Page » Next Page »

RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channels: Come and chat with us in real time

New to This Site? Here Are Some Introductory Resources

No

Mono

ODF

Samba logo






We support

End software patents

GPLv3

GNU project

BLAG

EFF bloggers

Comcast is Blocktastic? SavetheInternet.com



Recent Posts