Should have not trusted a third party to install proprietary code into the kernel. It’s not a Windows issue directly, they have a Linux version too, but anything that allows third parties to put proprietary code into your kernel and automatically update it without your approval is untrustworthy.
The cause is a malfunction of the Crowdstrike monitoring solution, which employees use to spy at anything ever done on company hardware. They do have a Linux version and it has been reported to cause kernel panics (not sure if during this incident).
But yes, Windows on public information displays is dumb.
it was because crowdstrike themselves notified that this specific instance did not affect their linux nor osx distributions of security, and was windows specific.
Should have used Linux!
Should have not trusted a third party to install proprietary code into the kernel. It’s not a Windows issue directly, they have a Linux version too, but anything that allows third parties to put proprietary code into your kernel and automatically update it without your approval is untrustworthy.
Counterpoint: Windows bad.
I can’t disagree with you there.
The cause is a malfunction of the Crowdstrike monitoring solution, which employees use to spy at anything ever done on company hardware. They do have a Linux version and it has been reported to cause kernel panics (not
sure ifduring this incident).But yes, Windows on public information displays is dumb.
it was because crowdstrike themselves notified that this specific instance did not affect their linux nor osx distributions of security, and was windows specific.
This in particular is a Crowdstrike issue. They suck as much as windows. Crowdstrike has had issues on Linux before:
Crowdstrike - freezing RockyLinux After 9.4 upgrade:: https://forums.rockylinux.org/t/crowdstrike-freezing-rockylinux-after-9-4-upgrade/14041
Kernel panic observed after booting 5.14.0-427.13.1.el9_4.x86_64 by falcon-sensor process:
https://access.redhat.com/solutions/7068083
Debian user experience: https://news.ycombinator.com/item?id=41005936
Another windows story: https://www.thestack.technology/crowdstrike-bug-maxes-out-100-of-cpu-requires-windows-reboots/