this post was submitted on 21 Aug 2024
162 points (98.2% liked)

Linux

5385 readers
252 users here now

A community for everything relating to the linux operating system

Also check out [email protected]

Original icon base courtesy of [email protected] and The GIMP

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 39 points 3 months ago (5 children)

Waiting for the MS apologists to say this is a Crowdstrike problem or some other fucking dumbass shit.

Microsoft by and large are just computational cancer at this point. Bloat, crud, fud, and junk.

[–] BatmanAoD 4 points 3 months ago (4 children)

The Crowdstrike problem was in fact a Crowdstrike problem. It affected Linux too, but of course there are vastly fewer users of Crowdstrike on Linux: https://www.google.com/amp/s/www.theregister.com/AMP/2024/07/21/crowdstrike_linux_crashes_restoration_tools/

This is pretty obviously a Microsoft problem.

[–] [email protected] 1 points 3 months ago (3 children)

Well… yes and no.

The fact that Crowdstrike very obviously and intentionally fuzzed the line between ring 0 drivers and app metadata simply could not have been done without MS’s tacit (at the very least) approval. The initial version where Cloudstrike introduced that side loading threat definition update vector should have been flagged as an issue - more specifically, they should have held them to a FAR more rigorous testing and resiliency standard than they were. This is fairly standard practice (and in many cases enforced as regulatory measures) for highly critical systems and components in a lot of industries, and I’ve worked in two of those industries.

[–] BatmanAoD 3 points 3 months ago

Yeah, that part is pretty wild and definitely Microsoft's fault.

load more comments (2 replies)
load more comments (2 replies)
load more comments (2 replies)