• he/him

I occasionally write long posts but you should assume I'm talking out of my ass until proved otherwise. I do like writing shit sometimes.  

 

50/50 chance of suit pictures end up here or on the Art Directory account. Good luck.

 

Be 18+ or be gone you kids act fuckin' weird.

 

pfp by wackyanimal


 

I tag all of my posts complaining about stuff #complaining, feel free to muffle that if you'd like a more positive cohost experience.

 


 
Art and suit stuff: @PlumPanAD

 


 
"DMs":
Feel free to message as long as you have something to talk about!


plumpan
@plumpan
  • We updated definitions file (but we call it something cooler) and it blew up the kernel.
  • We update this file multiple times a day and we're not going to stop doing it.
  • The file you have to delete isn't a driver! It totally isn't read by a driver that completely fucking broke the kernel!
  • The file is just evaluating every fucking pipe in the system no biggie.
  • We haven't decided who to throw under the bus yet even though the only way we could have done a fuckup this big was to have multiple policies and procedures fail massively or not exist in the first place.
  • Good luck!

Any company that does not dump crowdstrike after this deserves to have another outage


plumpan
@plumpan

Also like, this is the warning for every IT department out there. You have no excuses to not take action from Monday forward.

If you let someone else control how and when your systems update, and they're not responsible for personally going out to unfuck your systems if they push something bad, you're asking for major outages. Doesn't matter if it's crowdstrike, microsoft, or fucking canonical. They will push things out untested. They will use you as a test environment. They will not help when they break your stuff.

Unless you'd rather do the "we made sure our contract says if you break something we're going to be paid well, and we have an in house legal department to make sure of that" thing, I guess.


You must log in to comment.

in reply to @plumpan's post:

usually people are using crowdstrike for regulatory compliance so it isn't that easy.

this is a story, basically, of crowdstrike gobbling up the competent people and then laying them off last year, and there not being that much left that's actually... not terrible

Then maybe everyone needs to have a very serious discussion about what "regulatory compliance" means if it's just something saying "hey you need to go buy from one of these four rubber stamp vendors or we'll sue you".

Also like, I'm not familiar with exactly which compliance this would be but I hope "let them push updates whenever they want" is not part of that. "Don't let your systems go out of date" is fine but if you can't be 100% sure of updates happening in some sort of staggered fashion or doing some sort of internal testing before things get pushed out to every system you run, you're asking for trouble. That's basically the point I'm getting at.

unfortunately people have been talking about the various problems here for about 4 decades in a row, but the same stuff is still there

basically anything medical or that interfaces with the US federal system or military needs to be approved, and the way you get approved is basically by being loud and having a lot of schmoozing money, not being competent https://www.crowdstrike.com/why-crowdstrike/crowdstrike-compliance-certification/

same with EU, same with AU and APEC

we gotta change gov and how corporate-gov interface works, not how IT does :\ (there's other reasons to change IT, but I don't think anyone this decade* goes "we should get crowdstrike because I personally recommend it" or even "I refuse because there are other options")