Note about Crowdstrike Update PC Outage

This is the widespread IT outage last week that shut down air travel, stopped banking and other transactions, and generally fux0red the economy somewhat.

Crowdstrike makes IT security software apparently.

But they are an "old friend" to us. Crowdstrike was one of the parties that created the Russian collusion narrative about Trump.

https://www.bitchute.com/video/mUAxzvknf6WR

And Crowdstrike was alleged to have provided IT infrastructure for funneling ballots from the 2020 general election to other nations and then back to the US.

IMO Crowdstrike is a tool of the deep state to disrupt business and services as necessary within the US.

Now go read about their CEO and where he used to work.

Its very eye opening.

If you go to the tech department of almost every large corporation, it's almost 100% Indian with some Chinese and Russian thrown in sometimes.

It wouldn't be too hard to send spies pretending to be immigrant tech workers to sabotage the US economy. If I figured this out, you can bet spy agencies in China/Russia/India also figured this out.

Penetrate one company, push an update and ta-da - instant chaos.

So just think, a buggy DLL probably crashed 1/4 of the world economy briefly. Geekdom has come of age.

If a buggy DLL can crash 1/4 of the country's computers, imagine how great intentional sabotage would be.

It's good to get back to my developer roots.

Or in the case of Indians, debeloper.

[image]

lol

I saw a video that had a hex dump of the purported .SYS file which did the damage. Basically, the sys file was all nulls.

I've seen a couple of things which support that assertion, that the sys file was zeros.

So the official claim is that a null sys file was copied to countless Windows machines worldwide, causing airlines etc all over the world to fall over.

I don't believe a word of it.

In the unix world but also in the windows world, there is this concept that a downloadable file has a hash so that by the downloader checking the hash of his just-downloaded file against the vendor's published hash, the downloader can have some confidence that the file that he has just downloaded is legitimate. However, the hash of an all-zeros file is going to look very odd. So the person at Crowdstrike who was about to sign off the sys file for publishing would have noticed the dodgy hash.

This particular sys file has to be installed on a windows machine at a very low level (or, if you prefer, a very high level of access but I'm a programmer and to me lowest level means closest to the metal). So Microsoft's operating systems programmers do not allow any old file to replace a critically important system file without various checks. In fact I would go further and say that the OS has been written to not permit any part of itself to be replaced without passing a gauntlet of checks.

There are other things as well but without spending any further words, I do not believe that an all-zeros file replaced an existing system file without assistance from a human at one or more points in the chain.

These companies that update their software when updates are available from the vendor... do none of them apply the update to a small number of machines, check for problems in their own circumstances and only when satisfied that there are no such problems, roll out the update to a larger set of machines and ultimately to all machines in the company?

For such a large number of very large companies worldwide to fall over, the only possibility is that they all have incompetent systems administrators.

I don't believe it.

These companies that update their software when updates are available from the vendor... do none of them apply the update to a small number of machines, check for problems in their own circumstances and only when satisfied that there are no such problems, roll out the update to a larger set of machines and ultimately to all machines in the company?

For such a large number of very large companies worldwide to fall over, the only possibility is that they all have incompetent systems administrators.

I don't believe it.

Agreed. Most companies have a test bed where they roll these things out. Or I thought they did.

Though I saw a bunch of guys on another forum said that in their companies they dont do it.

I can absolutely believe that some companies don't do it properly. I can even guarantee it if you'll take my guarantee :)

But the sheer number and size of the companies we saw fall over, I do not believe.

Kudo the second. You're on a roll.

Enterprise updates are double checked to death. The risk of damage to IT is just too great to cowboy it, and that is what the Crowdstrike people seem to be saying happened.

This was a planned, deliberate sabotage.

A warning shot after the RNC?

Strokes chin - YES could be.

Good call. I bet you're right.

Crowdstrike didn't have a whoopsie with a bad DLL. Their explanation is so specific that it is absolute that they are lying. They explained too much. If they kept their mouths shut it would not be noted.

They were instructed to take a dump on key sectors of the economy.

What are your thoughts on how it transpired. Do you accept there was a null file and it was what followed that was kabuki, or the null file itself was a fiction and what went on was something completely different.

or the null file itself was a fiction and what went on was something completely different.

The latter - the quoted part. Probably a signal that we have angered the "gods" by letting Trump live.

Look at the company name itself, "Crowdstrike". Strike at a crowd? Very memetic.

As I said, if Crowdstrike had not tried to explain the supposed update fault, which explanation was hokey as hell, we wouldn't even be talking about this.

I believe the Crowdstrike outage was deliberate, was manufactured, was not an error, and more is to come.

the null file itself was a fiction

yep me too. And it's so obviously bullshit that probably it was a signal of some sort. "You got no hope" perhaps.

Look at the company name itself, "Crowdstrike". Strike at a crowd? Very memetic.

Very memetic. But if that was intentional, it was a very long plan. Crowdstrike has been around for yonks. They covered up the DNC "hack". That was eight years ago.

,ndo, you posted a description of the problem that is the first I've read. I haven't seen anyone else comment on that file of nuls explanation.

Kudos - insightful as f**k and totally legit.

A file full of NULs would elicit an LOL exception (basically) from the OS. The OS would essentially say "you're trying to install that crap? Geddowdahere!"

Has anyone seen an alternative narrative, or is the file full of nulls the accepted story?

I've seen that LOL exception:

The exception laughable software exception (0xc000004c) occurred in the application at location 0x004c4f4c.

Click on OK to humiliate the program.

RSS Feed of thread

P.A.G.A.N. - People Against Goodness And Normalcy

Note about Crowdstrike Update PC Outage (Public Board)

Can Also Be H1b Abuse

They Just Demonstrated How Easy It Is

They Just Demonstrated How Easy It Is

They Just Demonstrated How Easy It Is

They Just Demonstrated How Easy It Is

Is That A Screen Shot From Your System (NT)?

I was working on it... dust off MSVC 6.0

The whole thing is a con

I will add one thing

I will add one thing

I will add one thing

Yup

Yup

Warning shot?

Yup

Muh thoughts

Muh thoughts

Thanks for the critical analysis

anyone seen a different official narrative?

Thanks for the critical analysis