981–990 of 1001 posts
why the fuck is our critical infrastructure running on WINDOWS. Fuck the sad state of IT. CIOs and CTOs across the board need to be fired and held accountable for their shitty decisions in these industries. yes CRWD is a shitty company but seems they are a "necessity" by some stupid audit/regulatory board that oversees these industries. But at the end of the day, these CIOs/CTOs are completely fucking clueless as to…
Throwaway account... CrowdStrike in this context is a NT kernel loadable module (a .sys file) which does syscall level interception and logs then to a separate process on the machine. It can also STOP syscalls from working if they are trying to connect out to other nodes and accessing files they shouldn't be (using some drunk ass heuristics). What happened here was they pushed a new kernel driver out to every client…
Crowdstrike 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…
just sayin'
"Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp."
(https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule)
Arthur C. Clarke's third law:
"Any sufficiently advanced technology is indistinguishable from magic."
(https://en.wikipedia.org/wiki/Clarke%27s_three_laws#:~:text=....)
Apparently we now have the following, as well:
"Any sufficiently bad software update is indistinguishable from a cyberattack…"
Chances if Microsoft or Crowdstrike will be held liable for financial losses caused by this outage?