this post was submitted on 19 Jul 2024
1279 points (100.0% liked)

Programmer Humor

21779 readers
2068 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
top 50 comments
sorted by: hot top controversial new old
[–] Logh@lemmy.ml 136 points 8 months ago (3 children)

Funny how CrowdStrike already sounds like some malware’s name.

[–] dmention7@lemm.ee 76 points 8 months ago (1 children)

It literally sounds like a DDoS!

[–] bruhduh@lemmy.world 22 points 8 months ago

Botnet if you will

[–] SkyNTP@lemmy.ml 24 points 8 months ago (2 children)

Not too surprising if the people making malware, and the people making the security software are basically the same people, just with slightly different business models.

load more comments (1 replies)
load more comments (1 replies)
[–] Carighan@lemmy.world 133 points 8 months ago (2 children)

This is, in a lot of ways, impressive. This is CrowdStrike going full "Hold my beer!" about people talking about what bad production deploy fuckups they made.

[–] henfredemars@infosec.pub 93 points 8 months ago (1 children)

You know you’ve done something special when you take down somebody else’s production system.

[–] bruhduh@lemmy.world 23 points 8 months ago (1 children)

*production systems around whole world

load more comments (1 replies)
[–] KomfortablesKissen@discuss.tchncs.de 26 points 8 months ago (1 children)

I'm volunteering to hold their beer.

Everyone remember to sue the services not able to provide their respective service. Teach them to take better care of their IT landscape.

[–] ricecake@sh.itjust.works 25 points 8 months ago (1 children)

Typically auto-applying updates to your security software is considered a good IT practice.

Ideally you'd like, stagger the updates and cancel the rollout when things stopped coming back online, but who actually does it completely correctly?

[–] KomfortablesKissen@discuss.tchncs.de 21 points 8 months ago (1 children)

Applying updates is considered good practice. Auto-applying is the best you can do with the money provided. My critique here is the amount of money provided.

Also, you cannot pull a Boeing and let people die just because you cannot 100% avoid accidents. There are steps in between these two states.

[–] ricecake@sh.itjust.works 28 points 8 months ago (2 children)

you cannot pull a Boeing and let people die

You say that, but have you considered the savings?

[–] Iheartcheese@lemmy.world 21 points 8 months ago

People are temporary. Money is forever.

[–] KomfortablesKissen@discuss.tchncs.de 7 points 8 months ago* (last edited 8 months ago) (1 children)

I have. They are not mine. The dead people could be.

Edit: I understand you were being sarcastic. This is a topic where I chose to ignore that.

[–] ricecake@sh.itjust.works 8 points 8 months ago (12 children)

That's totally fair. :)

I work at a different company in the same security space as cloudstrike, and we spend a lot of time considering stuff like "if this goes sideways, we need to make sure the hospitals can still get patient information".

I'm a little more generous giving the downstream entities slack for trusting that their expensive upstream security vendor isn't shipping them something entirely fucking broken.
Like, I can't even imagine the procedureal fuck up that results in a bsod getting shipped like that. Even if you have auto updates enabled for our stuff, we're still slow rolling it and making sure we see things being normal before we make it available to more customers. That's after our testing and internal deployments.

I can't put too much blame on our customers for trusting us when we spend a huge amount of energy convincing them we can be trusted to literally protect all their infrastructure and data.

load more comments (12 replies)
[–] Legendarylootz 104 points 8 months ago (2 children)

The real malware is the security software we made along the way.

[–] WhiskyTangoFoxtrot@lemmy.world 39 points 8 months ago (1 children)

We've known that since Norton and McAfee.

[–] mnemonicmonkeys@sh.itjust.works 11 points 8 months ago (1 children)

At least McAfee's antics were entertaining

load more comments (1 replies)
load more comments (1 replies)
[–] psycho_driver@lemmy.world 49 points 8 months ago (4 children)

The answer is obviously to require all users to change their passwords and make them stronger. 26 minimum characters; two capitals, two numbers, two special characters, cannot include '_', 'b' or the number '8', and most include Pi to the 6th place.

[–] ulterno@lemmy.kde.social 9 points 8 months ago

Great! Now when I brute force the login, I can tell my program to not waste time trying '_', 'b' and '8' and add Pi to the 6th place in every password, along with 2 capitals, 2 numbers and 2 other special characters.

Furthermore, I don't need to check passwords with less than 26 characters.

load more comments (3 replies)
[–] clearedtoland@lemmy.world 24 points 8 months ago

What’s the saying about dying a hero or becoming the villain?

[–] aniki@lemmy.zip 20 points 8 months ago (6 children)

ItS NoT A wInDoWs PrObLeM -- Idiots, even on Lemmy

[–] ricdeh@lemmy.world 47 points 8 months ago

I genuinely can't tell at whom you are addressing this. Those claiming it is a Windows problem or those that say otherwise?

[–] jet@hackertalks.com 33 points 8 months ago* (last edited 8 months ago) (7 children)

You can not like windows, and also recognize that CrowdStrike isn't from Microsoft - so a problem that CrowdStrike caused isn't the fault of Windows.

If that makes me a idiot by holding two different ideas in my head, so be it, but you are spending time with us, so thank you for elevating us!

[–] Azzu@lemm.ee 21 points 8 months ago

I'm sorry, but distinguishing between different concepts is forbidden here. You go straight to jail.

load more comments (6 replies)
[–] daellat@lemmy.world 28 points 8 months ago (2 children)

Hi, idiot here. Can you explain how it is a windows problem?

[–] Kusimulkku@lemm.ee 27 points 8 months ago (1 children)

It's a problem affecting Windows, not problem caused by Windows I guess.

load more comments (1 replies)
[–] aniki@lemmy.zip 7 points 8 months ago* (last edited 8 months ago) (1 children)

If you patch a security vulnerability, who's fault is the vulnerability? If the OS didn't suck, why does it need a 90 billion dollar operation to unfuck it?

Redhat is VALUED at less than that.

https://pitchbook.com/profiles/company/41182-21

It's a fucking windows problem.

[–] ricecake@sh.itjust.works 50 points 8 months ago* (last edited 8 months ago) (7 children)

Sure, but they weren't patching a windows vulnerability, windows software, or a security issue, they were updating their software.

I'm all for blaming Microsoft for shit, but "third party software update causes boot problem" isn't exactly anything they caused or did.

You also missed that the same software is deployed on Mac and Linux hosts.

Hell, they specifically call out their redhat partnership: https://www.crowdstrike.com/partners/falcon-for-red-hat/

[–] xtr0n@sh.itjust.works 14 points 8 months ago (2 children)

Crowdstrike completely screwed the pooch with this deploy but ideally, Windows wouldn’t get crashed by a bas 3rd party software update. Although, the crashes may be by design in a way. If you don’t want your machine running without the security software running, and if the security software is buggy and won’t start up, maybe the safest thing is to not start up?

[–] MangoPenguin@lemmy.blahaj.zone 22 points 8 months ago (1 children)

Are we acting like Linux couldn't have the same thing happen to it? There are plenty of things that can break boot.

CrowdStrike also supports Linux and if they fucked up a Windows patch, they could very well fuck up a linux one too. If they ever pushed a broken update on Linux endpoints, it could very well cause a kernel panic.

[–] ricecake@sh.itjust.works 14 points 8 months ago (1 children)

Yeah, it's a crowd strike issue. The software is essentially a kernel module, and a borked kernel module will have a lot of opportunities to ruin stuff, regardless of the OS.

Ideally, you want your failure mode to be configurable, since things like hospitals would often rather a failure with the security system keep the medical record access available. :/. If they're to the point of touching system files, you're pretty close to "game over" for most security contexts unfortunately. Some fun things you can do with hardware encryption modules for some cases, but at that point you're limiting damage more than preventing a breach.

Architecture wise, the windows hybrid kernel model is potentially more stable in the face of the "bad kernel module" sort of thing since a driver or module can fail without taking out the rest of the system. In practice.... Not usually since your video card shiting the bed is gonna ruin your day regardless.

load more comments (1 replies)
load more comments (6 replies)
[–] GBU_28@lemm.ee 22 points 8 months ago (1 children)

"even on Lemmy"

Like this is some highbrow collection of geniuses here?

load more comments (1 replies)
[–] Cornelius_Wangenheim@lemmy.world 21 points 8 months ago* (last edited 8 months ago) (7 children)

Because it isn't. Their Linux sensor also uses a kernel driver, which means they could have just as easily caused a looping kernel panic on every Linux device it's installed on.

load more comments (7 replies)
load more comments (1 replies)
[–] Solemarc@lemmy.world 17 points 8 months ago (3 children)

Maybe this is a case of hindsight being 20/20 but wouldn't they have caught this if they tried pushing the file to a test machine first?

[–] tabularasa@lemmy.ca 13 points 8 months ago (1 children)

It's not hindsight, it's common sense. It's gross negligence on CS's part 100%

load more comments (1 replies)
[–] Gsus4@programming.dev 13 points 8 months ago (1 children)

I saw one rumor where they uploaded a gibberish file for some reason. In another, there was a Windows update that shipped just before they uploaded their well-tested update. The first is easy to avoid with a checksum. The second...I'm not sure...maybe only allow the installation if the windows update versions match (checksum again) :D

load more comments (1 replies)
load more comments (1 replies)
[–] slazer2au@lemmy.world 15 points 8 months ago (1 children)

Now threat actors know what EDR they are running and can craft malware to sneak past it. yay(!)

[–] marcos@lemmy.world 8 points 8 months ago

Smart threat actors use the EDR for distribution. Seems to be working very well for whoever owned Solar Winds.

[–] jet@hackertalks.com 14 points 8 months ago

A real Anakin arc right here.

[–] pkill@programming.dev 11 points 8 months ago

SHOULD'VE USED OPENBSD LMAO

[–] Ptsf@lemmy.world 9 points 8 months ago* (last edited 8 months ago)
[–] baggins@lemmy.ca 7 points 8 months ago (1 children)

Yes but the difference is one of them is also going to help you fix it.

load more comments (1 replies)
load more comments