Earlier quoted context omitted.
Also it's the _second_ time that they had done this in a few short months. They had previous bricked linux hosts earlier with a similar type of update. So we also know that they don't learn from their mistakes.
The blame for the Linux situation isn’t as clear cut as you make it out to be. Red hat rolled out a breaking change to BPF which was likely a regression. That wasn’t caused directly by a crowdstrike update.
CrowdStrike ex-employees: 'Quality control was not part of our process'
111–120 of 311 posts
Re: CrowdStrike ex-employees: 'Quality control was not part of our process'
#112What are some alternatives to CrowdStrike?
Personal: Nothing - Windows Defender is built into Windows. Business: Nothing - Windows Defender Advanced Threat Protection is built into the higher Microsoft 365 license tiers. It amazes me people chose to pay money to have all their PCs bluescreen.
Re: CrowdStrike ex-employees: 'Quality control was not part of our process'
#113Earlier quoted context omitted.
Conspiracy theory time. Because Apple is the only OS company that has reliably proven that it won't decrypt hard drives at government request.
It depends on the country it is in, it rejects the US government's request. But it fully complies with any request from the Chinese government
My mental model was that Apple provides backdoor decryption keys to China in advance for devices sold in China/Chinese iCloud accounts, but that they cannot/will not bypass device encryption for China for devices sold outside of the country/foreign iCloud accounts.
Re: CrowdStrike ex-employees: 'Quality control was not part of our process'
#114What are some alternatives to CrowdStrike?
Re: CrowdStrike ex-employees: 'Quality control was not part of our process'
#115Earlier quoted context omitted.
Ideally secrets never leave secure enclaves and humans at the organization can't even access them. It's totally insane to send them to a remote service controlled by another organization.
Essentially, it’s straddling two extremes: 1) employees are trusted with secrets, so we have to audit that employees are treating those secrets securely (via tracking, monitoring, etc) 2) we don’t allow employees to have access to secrets whatsoever, therefore we don’t need any auditing or monitoring
It works the same way for biometrics like face unlock on mobile phones
Re: CrowdStrike ex-employees: 'Quality control was not part of our process'
#116Re: CrowdStrike ex-employees: 'Quality control was not part of our process'
#117Earlier quoted context omitted.
Why would you trust a company no-man any more than a company yes-man? They both have agendas and biases. Is it just that you personally prefer one set of biases (anti-company) more than the other (pro-company)?
Yes, I am very much biased toward being anti-company and I make no apologies for that. I've been in the corporate world long enough to know first-hand the sins that PR and corporate management commits on the company's behalf and the harm it does. I find information coming from the individual more reliable than having it filtered through corpo PR, legal, ass-covering nonsense, the latter group often wanting to preserv…
Re: CrowdStrike ex-employees: 'Quality control was not part of our process'
#118Earlier quoted context omitted.
Ideally secrets never leave secure enclaves and humans at the organization can't even access them. It's totally insane to send them to a remote service controlled by another organization.
Essentially, it’s straddling two extremes: 1) employees are trusted with secrets, so we have to audit that employees are treating those secrets securely (via tracking, monitoring, etc) 2) we don’t allow employees to have access to secrets whatsoever, therefore we don’t need any auditing or monitoring
Re: CrowdStrike ex-employees: 'Quality control was not part of our process'
#119Re: CrowdStrike ex-employees: 'Quality control was not part of our process'
#120Earlier quoted context omitted.
Why would a UX designer be involved in any way, shape, or form in kernel level code patches? They would literally never ship an update if they had that many hands in the pot for something completely unrelated. Should they also have their sales reps and marketing folks pre-brief before they make any code changes?
A UX designer might have told them it was a bad idea to deploy the patch widely without testing a smaller cohort, for instance. That’s an obvious measure that they skipped this time.