closed source will always fuck you in the ass
CrowdStrike Update: Windows Bluescreen and Boot Loops
801–810 of 1001 posts
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#802There is hardly a better time if you write software to watch - "The Mess We're In" by Joe Armstrong - https://www.youtube.com/watch?v=lKXe3HUG2l4
I am not sure in which one of his talks he briefly mentioned that one of his concerns is that we are basically building a digital Alexandria library, and if it burns, well ...
Even more devastating events like this will happen in the future.
We stand on the shoulders of giants and yet we learned nothing.
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#803Texas, where software goes to die. Or maybe that is where killer software is developed?
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#804Crowdstrike did this to our production linux fleet back on April 19th, and I've been dying to rant about it. The short version was: we're a civic tech lab, so we have a bunch of different production websites made at different times on different infrastructure. We run Crowdstrike provided by our enterprise. Crowdstrike pushed an update on a Friday evening that was incompatible with up-to-date Debian stable. So we patc…
[flagged]
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#805This might be a good time for folks to go back and watch the first episode of James Burke's Connections: The Trigger Effect https://www.youtube.com/watch?v=NcOb3Dilzjc Interconnected systems can fail spectacularly in unforeseen ways. Strange that something so obvious is so often dismissed or overlooked.
Again, as I feel I must every time Connections is mentioned: That series is an unmitigated masterpiece. It really is ...
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#806Now things are serious: I can't place a mobile order at Starbucks.
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#807Is there a way to estimate number of affected devices? 10 million? 100 million?
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#808This might be a good time for folks to go back and watch the first episode of James Burke's Connections: The Trigger Effect https://www.youtube.com/watch?v=NcOb3Dilzjc Interconnected systems can fail spectacularly in unforeseen ways. Strange that something so obvious is so often dismissed or overlooked.
My issue is WTF do sooooooo many companies trust this 1 fucking company lol, like its always some obscure company that every major corporation is trusting lol. All because crowdstrike apparently throws good parties for C-Level execs lol
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#809It should be obvious to everyone now that kernel extensions for ‘security’ is not worth it
Re: CrowdStrike Update: Windows Bluescreen and Boot Loops
#810Wow, this hits close to home. Doing a page fault where you can't in the kernel is exactly what I did with my very first patch I submitted after I joined the Microsoft BitLocker team in 2009. I added a check on the driver initialization path and didn't annotate the code as non-paged because frankly I didn't know at the time that the Windows kernel was paged. All my kernel development experience up to that point was wi…
https://news.ycombinator.com/item?id=41006104#41006555
the flawed data was added in a post-processing step of the configuration update, which is after it's been tested internally but before it's copied to their update servers
per a new/green account