Man of Honour
It's only the MS platform, isn't it?
Yeah; Mac and Linux has been unaffected
It's only the MS platform, isn't it?
Just imagine being the programmer who wrote this update and waking up the next day to all this.......
I think they were batched, but it was a fully automated deployment / test system (rebuilding test environments etc.) anyway.That's a shed load of additional work for a team considering those updates are daily if not multiple times a day
just exposes companies who don't have hygienic software deployment schemes
... so if the genuine russian pirates had done some kind of dns intrusion to deploy a bogus release, having hacked appropriate certificates
It's been a few years since I did much work with Windows servers, but I don't understand why this has affected so many companies - I'd normally expect updates to be tested in staging / pre-production environments before going to a live system
Did all these companies have Cloudstrike automatic updates on in production systems? That seems pretty crazy to me!
one of the major benefits of WFHYou having a stroke again?
what happened you got hit because you didn't have any TP (using Beavis's vernacular)You having a stroke again?
Apparently they were trying to fix the Sonos app
It really cant be right that one software glitch from one company has caused so much disruption globally - Govts/companies need to take a hard look at the situation we seem to have put ourselves in.
It really cant be right that one software glitch from one company has caused so much disruption globally - Govts/companies need to take a hard look at the situation we seem to have put ourselves in.
An anti virus company will be making 100s of releases a month - current products, previous products and the fact that the anti virus business is very dynamic considering its prey. The number of configurations for Windows software is insane - I have no doubts that this would have been thoroughly tested but you can't have 100% coverage for the millions (billions?!) of configurations for MS platforms - the hardware, the software, the different versions, the different drivers / applications on that machine. Will be really interesting to know what the actually problem was (if we'll ever be told) but bugs like this are constantly released into the wild. It's just this time it caused BSOD.The question is who approved it. Lone programmers don't release code in this size IT firm, this is a massive failure that would involve multiple people, from the people who coded it, the testers and the managers who approved the code commits and patch releases