DesertCreosote

@DesertCreosote@lemm.ee

• ⁨Comment⁩ on ⁨We really should have all seen this coming.⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  Unfortunately the amount of delta-V you’d need to boost it to a parking orbit of some kind, or to the moon, would be deeply impractical. And it doesn’t have the shielding required to support any sort of deep space habitation.

  I’d love to see some or all of it returned to be displayed in a museum, but it would probably be more expensive to do that than it was to build it in the first place. The vehicles to return it in whole or in pieces simply don’t exist right now, and on-orbit disassembly would be incredibly difficult and dangerous for astronauts to carry out.

• ⁨Comment⁩ on ⁨CrowdStrike Isn't the Real Problem⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  I’m one of the admins who manage CrowdStrike at my company.

  We have all automatic updates disabled, because when they were enabled (according to the CrowdStrike best practices guide they gave us), they pushed out a version with a bug that overwhelmed our domain servers. Now we test everything through multiple environments before things make it to production, with at least two weeks of testing before we move a version to the next environment.

  This was a channel file update, and per our TAM and account managers in our meeting after this happened, there’s no way to stop that file from being pushed, or to delay it. Supposedly they’ll be adding that functionality in now.

• ⁨Comment⁩ on ⁨CrowdStrike Isn't the Real Problem⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  Yes, CrowdStrike says they don’t need to do conventional AV definitions updates, but the channel file updates sure seem similar to me.

  The file they pushed out consisted of all zeroes, which somehow corrupted their agent and caused the BSOD. I wasn’t on the meeting where they explained how this happened to my company; I was one of the people woken up to deal with the initial issue, and they explained this later to the rest of my team and our leadership while I was catching up on missed sleep.

  I would have expected their agent to ignore invalid updates, which would have prevented this whole thing, but this isn’t the first time I’ve seen examples of bad QA and/or their engineering making assumptions about how things will work. For the amount of money they charge, their product is frustratingly incomplete. And asking them to fix things results in them asking you to submit your request to their Ideas Portal, so the entire world can vote on whether it’s a good idea, and if enough people vote for it they will “consider” doing it. My company spends a fortune on their tool every year, and we haven’t been able to even get them to allow non-case-sensitive searching, or searching for a list of hosts instead of individuals.

• ⁨Comment⁩ on ⁨CrowdStrike Isn't the Real Problem⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  Speaking as someone who manages CrowdStrike in my company, we do stagger updates and turn off all the automatic things we can.

  This channel file update wasn’t something we can turn off or control. It’s handled by CrowdStrike themselves, and we confirmed that in discussions with our TAM and account manager at CrowdStrike while we were working on remediation.