Greek Opposition recommends adopting Linux following the Crowdstrike event.
Greek Opposition recommends adopting Linux following the Crowdstrike event.
It's a common scenario when major security firms release updates that affect Linux—everyone ends up facing similar challenges. This isn't due to Windows being the only platform involved; it's because Crowdstrike's recent changes disrupted Linux. The real solution lies in spreading risk across multiple operating systems, rather than concentrating everything in one system.
They're proposing a shift from Crowdstrike on Windows to Crowdstrike on Linux. This change aims to address the issue you mentioned, though it's unclear exactly what it resolves. You seem to be curious about this update.
A small patch from Crowdstrike led to a broken Windows version. I back their move to Linux, but they shouldn’t continue relying on Crowdstrike. It’s better to have your own IT team manage the situation.
The best solution is avoiding full reliance on a single software, security layer, or operating system by employing multiple options or swapping them during startup.
Several seasoned IT/tech/programmer professionals expressed their concerns about IT administrators relying solely on Windows for infrastructure management. Many misunderstand the root cause, thinking it was exclusively a Microsoft issue, when in reality it stems largely from Crowd Strike. While GNU/Linux offers advantages—especially for server-side tasks—it isn't immune to similar challenges. The real benefit lies in avoiding over-reliance on a single platform and leveraging Linux as an alternative or switching seamlessly during issues.
The problem isn't related to Windows. It stems from security software tightly embedded in the operating system, allowing developers to push updates universally without customer approval. If users switch to Linux but rely on an external vendor who installs updates without oversight, similar issues will recur. To prevent this, customers should: choose a provider that rigorously checks updates before release, verify updates in their own testing setup before deployment, release updates slowly starting with non-critical systems. This approach would likely raise costs and effort significantly. Plus, security patches for software often need urgent attention (e.g., zero-day exploits), creating pressure to update quickly and bypass testing—just one time, I assure you. What if you postpone the update for more testing while your production systems are targeted…?
Here, windows isn't responsible for the issue (lol), but the product itself is. Switching to another OS won't fix it, though linux tends to be more secure and reliable overall. I think a system built with a microkernel without compromises—especially avoiding message overhead compared to syscalls—would perform much better for both business and everyday users.
What puzzled me was how the situation unfolded during the Crowdstrike incident. I assumed bigger companies would manage most changes via Group Policy and could detect issues early enough to prevent widespread problems. While smaller or mid-sized firms might struggle, I expected larger businesses and some governments to have the necessary oversight. The fact that Crowdstrike released a breaking update without timely detection really baffled me.