this post was submitted on 20 Jul 2024
100 points (82.1% liked)

linuxmemes

20770 readers
2287 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
poopsmith@lemmy.world
zephyr@lemmy.world
100
Concerning CrowdStrike (infosec.exchange)
submitted 2 months ago by uis@lemm.ee to c/linuxmemes@lemmy.world
8 comments fedilink hide all child comments
 

We are now at t+26h. Please compare how much we knew about the xz-attack after less than a day with what we know about the chain of events of giant outage yesterday.

If something similar had been caused by an OSS component, we would see congress discussing a ban on open software in critical infrastructure already.

you are viewing a single comment's thread
view the rest of the comments
[–] slazer2au@lemmy.world 132 points 2 months ago (3 children)

If something similar had been caused by an OSS component, we would see congress discussing a ban on open software in critical infrastructure already.

No we won't. I refer to HeartBleed, Log4J, and Eternal Blue, and Solar winds. None of those affected applications have been banned and never will. Congress bans are based on political aspects not technical ones.

Huawei ban is because of the ties to China, kaspersky was banned because of Russian ties.

[–] Artyom@lemm.ee 24 points 2 months ago

Security vulnerabilities are a big deal in the tech world, but no one really cares outside of that. The CrowdStrike bug was big because it was user-facing and shut down systems. The truth is we haven't seen any user-facing bugs from open source software to compare CrowdStrike to.

[–] ProjectPatatoe@lemmy.world 1 points 1 month ago

But... if I don't propose a ban, everyone will think I don't know what i'm doing