this post was submitted on 19 Jul 2024
85 points (80.1% liked)
main
1335 readers
9 users here now
Default community for midwest.social. Post questions about the instance or questions you want to ask other users here.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Don't think this couldn't happen to Linux, it's not a Windows problem but a vendor problem.
Yes and no. Bitlocker is one of the core issues for recovery in many companies. Employees don't have access to the key, the key must be entered by hand and is long. And there are scaling issues.
Under linux you have different recovery options, and a secured bootloader password could be shared with all employees and changed afterwards. That is not a thing with windows
Linux doesn't force automatic updates into your system.
On windows, the changes go out to everyone all at once. You figure out there's a problem at the same time as everyone else on windows.
On Linux (with a good it department), pending app/os updates get pulled to testing machine, test to make sure it still works, have supported machines pull down that version.
This was a software update that a vendor pushed through their own means. The same thing can happen on Linux
Edit: Also windows has update rings that can do what you're describing
This is in no way unique to Linux.
As I said, this was a vendor issue, the vendor pushed an update that their software is configured to automatically download.
Also, Windows actually has several steps until updates get pushed out to the general public, beta channels, and staggered releases, etc. Plus any moderately sized company will have their own windows update server and a test bed of computers to test updates on. Windows is actually very enterprise friendly.
You manually load them up and pray the vendor didn't fuck up like this.