In our testing, the VPN always continued to report as connected, and the kill switch was never engaged to drop our VPN connection.
This is the only place they mention kill switch. I feel like it needs a slight clarification on whether it was enabled and didn’t work, or if was just disabled and therefore not “engaged”.
Just switch to GNU/Hurd
/s
They change it all the time for funsies
You can squash merge so it goes into the main branch as one commit, that’s usually how I do it.
You never do
I hope lemmy gets some super interesting posts that become core lore for the entire user base like this one was for reddit.
The more I learn about web3/crypto, it is increasingly getting closer to real life financials with all the same pitfalls and extra crypto problems
I don’t know why you’re being downvoted here. I thought a lot of the audience here was relatively informed on what it’s like to work in IT/programming. Where we do what we can to make sure all our updates go well, but things slip through the cracks.
This was a massive fuckup, but it’s likely not that different than pushing a bug to prod, it just so happens that their prod has such a huge audience. I would hope they have very strict rules about what gets in, but I can also respect that no matter how many processes you put in place to make sure bad things don’t happen, problems can still make it through.
Crowdstrike should be held to a higher standard of course, because of how impactful these mistakes can be for their software. And it’s pretty crazy that something this bad slipped through. But I wouldn’t jump to criminal negligence here without more information.
p.s. I’m not saying CEOs / corps should not be held accountable. They should be. And CEOs do have the power to drive the company into criminal acts and they should be held accountable with jail time for that. I’m just saying I don’t think that’s the case here.