Comment on CrowdStrike broke Debian and Rocky Linux months ago, but no one noticed
AlecSadler@sh.itjust.works 3 months agoSerious question, can you not? There isn’t an option to…like…set a review system first?
Comment on CrowdStrike broke Debian and Rocky Linux months ago, but no one noticed
AlecSadler@sh.itjust.works 3 months agoSerious question, can you not? There isn’t an option to…like…set a review system first?
EncryptKeeper@lemmy.world 3 months ago
For antivirus definitions? No, and you wouldn’t want to.
AlecSadler@sh.itjust.works 3 months ago
But it sounds like this added files / drivers or something, not just antivirus rules?
SeeJayEmm@lemmy.procrastinati.org 3 months ago
Turns out it was a content update that caused the driver to crash but the update itself wasn’t a driver (as per their latest update.)
wolfylow@lemmy.world 3 months ago
Found this post that explains what happened in detail: lemmy.ohaa.xyz/post/3522666
As an application developer (rather than someone who can/does code operating systems) I was just left open-mouthed …
Looks like they’re delivering “code as content” to get around the rigour of getting an updated driver authorised by MS. I realise they can’t wait too long for driver approval for antivirus releases but surely - surely - you have an ironclad QA process if you’re playing with fire like this.
b161@lemmy.blahaj.zone 3 months ago
Do you know if the sensor update policy had been set to N-2 would this have avoided the issue?
AlecSadler@sh.itjust.works 3 months ago
Oh, wow.
mox@lemmy.sdf.org 3 months ago
nitter.poast.org/…/1814343502886477857