Re: xkcd: CrowdStrike

On Tue, 23 Jul 2024 12:55:00 -0400, Cryptoengineer
<petertrei@gmail.com> wrote:

On 7/23/2024 12:27 PM, Paul S Person wrote:

On Tue, 23 Jul 2024 07:56:32 -0000 (UTC), Charles Packer
<mailbox@cpacker.org> wrote:
 

On Mon, 22 Jul 2024 16:01:25 -0500, Lynn McGuire wrote:
>

xkcd: CrowdStrike
     https://www.xkcd.com/2961/
>
Make the best of bad times.
>
Explained at:
     https://www.explainxkcd.com/wiki/index.php/2961:_CrowdStrike
>
Lynn

>
Was anybody here affected by the CrowdStrike Thing?
My nephew's wife flew to Europe that day without incident.

 
Not here. But then, I don't do that much on the Web. And I use Windows
10's security, which was not affected.
 
I saw an article where Microsoft was blaming the EU for forcing them
to allow 3rd-party access to the Kernal, which they claim is what
enabled the update to do bad things. If that is true, they may have a
point.

>
That requires a belief that Microsoft isn't just as capable of this
of SNAFU.

No it does not. But, if true, it /does/ mean that regulators trying to
break the Windows monopoly on certain classes of programs (well, what
those regulators perceive as a monopoly, anyway) need to consider how
risky what they are requiring is.

Allowing anybody who writes a security program to modify the kernal
does not sound particularly safe to me.

I don't have that belief.

Well, neither do I. At last! Agreement!

IIRC, there have been Win10 updates that produced problems similar to
this. Except, instead of not booting at all, the machines affected
booted again ... and again ... and again ... and again ...
Which is really just as bad.

But I've never been affected by them ... so far.

I did have to block a program I compile myself, generally at least
once a day, from Microsoft Defender because it flagged it:

6/16/23 (Severe – Quarantined):
Detected: Trojan:Win32/Sabsik.FL.B!ml
file: C:\ow\ow\bld\wgml\win32\wgml.exe

It was doing this sort of thing with a /lot/ of files that hadn't been
changed or recompiled for a long long time, but I didn't bother with
blocking those. It's not presently doing this, so apparently it was
"false positive" problem. Perhaps someone thought that a particular
executable file header was unique to viruses.
--
"Here lies the Tuscan poet Aretino,
Who evil spoke of everyone but God,
Giving as his excuse, 'I never knew him.'"