Technology

58138 readers

4398 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

255

Microsoft points finger at the EU for not being able to lock down Windows (www.neowin.net)

submitted 1 month ago by neme@lemm.ee to c/technology@lemmy.world

92 comments fedilink hide all child comments

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

[–] kescusay@lemmy.world -1 points 1 month ago* (last edited 1 month ago) (2 children)

~~The thing is, Microsoft's virus-scanning API shouldn't be able to BSOD anything, no matter what third-party software makes calls to it, or the nature of those calls. They should have implemented some kind of error handler for when the calls are malformed.~~

~~So this is really a case of both Crowdstrike and Microsoft fucking up. Crowdstrike shoulders most of the blame, of course, but Microsoft really needs to harden their API to appropriately catch errors, or this will happen again.~~

I'm an idiot. For some reason, I was thinking about the Windows Defender API, which can be called from third-party applications.

[–] Heavybell@lemmy.world 11 points 1 month ago (1 children)

I don't believe there was any specific API in use here, for virus scanning or not. I suppose maybe the device driver API? I am not a kernel developer so I don't know if that's the right term for it.

Crowdstrike's driver was loaded at boot and caused a null pointer dereference error, inside the kernel. In userspace, when this happens, the kernel is there to catch it so only the application that caused it crashes. In kernelspace, you get a BSOD because there's really nothing else to do.

https://youtube.com/watch?v=wAzEJxOo1ts

[–] kescusay@lemmy.world 5 points 1 month ago

I stand corrected. For some reason, I was thinking they used the actual Windows Defender API, which can be called programmatically from third-party applications, but you're correct, it was a driver loaded at boot. Microsoft isn't at all at fault, here.

[–] catloaf@lemm.ee 1 points 1 month ago (1 children)

Isn't that API what the article is talking about?

[–] kescusay@lemmy.world 2 points 1 month ago

Nope. It's a lower level kernel API that has to be accessed at boot via a driver. The API I was thinking of - and I use the term "thinking" loosely, here - is an API that userspace applications can take advantage of to scan files after boot is already complete.