this post was submitted on 20 Jul 2024
101 points (82.2% liked)

linuxmemes

21453 readers
1858 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
    poopsmith
    zephyr
    rtxn
    101
    Concerning CrowdStrike (infosec.exchange)
    submitted 4 months ago by [email protected] to c/linuxmemes
    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 132 points 4 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.

    [–] [email protected] 24 points 4 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 1 points 4 months ago

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