(no title)
jamescun | 1 year ago
I guess the only question they could answer is why they don't provide a framework like Apple do with Endpoint Security for third-party vendors to use.
jamescun | 1 year ago
I guess the only question they could answer is why they don't provide a framework like Apple do with Endpoint Security for third-party vendors to use.
Daviey|1 year ago
Linux has eBPF which can provide most of the capability that Crowdstrike needs, by using an "in-kernel verifier which performs static code analysis and rejects programs which crash, hang or otherwise interfere with the kernel negatively". If MS had this functionality, it is likely this incident would not have happened.
That said, from personal experience on Linux it's been an extremely long time since a bad kernel module has rendered a system entirely FUBAR'd.
(To Microsoft credit, they have begun copying the eBPF methodoloy to Windows, but it is still in it's infancy https://github.com/Microsoft/ebpf-for-windows/ ).
jcranmer|1 year ago
keneda7|1 year ago
netdevnet|1 year ago
It didn't stop Linux machines from being down so it is clearly not as easy as you put it. The reality is that writing software is hard yet devs often trivialise it to their own detriment
politelemon|1 year ago
"Serious questions to answer after what could be the biggest IT outage in history"
landr0id|1 year ago
landr0id|1 year ago
The only thing I could think of is if it was a driver update, the driver has to be "WHQL" signed. WHQL stands for "Windows Hardware Quality Lab" -- what quality are they ensuring? (spoiler alert from my time at Microsoft: it's not terribly robust :p )
It's not realistic for Microsoft to test drivers in a manner that represents real-world usage, but perhaps they need to start doing some basic "it works with whatever integrated agent/etc is required" testing as a requirement for signing a driver.
If it was a user-mode update? Yeah no real fault on Microsoft here.
KHRZ|1 year ago
drpossum|1 year ago
danbruc|1 year ago