Asklemmy

43893 readers

1306 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago

MODERATORS

160

What makes CrowdStrike so ubiquous that their error created such catastrophe? (sh.itjust.works)

submitted 4 months ago by pastermil@sh.itjust.works to c/asklemmy@lemmy.ml

47 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] CaptainBasculin@lemmy.ml 26 points 4 months ago (1 children)

Basically, drivers can launch code all the way up to ring 0, the highest level a code can access to. This mean it runs its code with the same priviledges as the kernel itself. The anti-malware solution CrowdStrike makes use of this access to determine what could be going wrong, and deploy solutions accordingly.

If a code running in that level crashes, Windows will rightfully assume there's something really fucked up is going on, and give out a BSOD.

[–] Blizzard@lemmy.zip 14 points 4 months ago (1 children)

there's something really fucked up going on

I would actually prefer this kind of error over the usual and equally uninformative "Oopsie! Something went wrong. We're sorry :("