this post was submitted on 19 Jul 2024
2017 points (99.1% liked)

linuxmemes

21210 readers
62 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!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    2017
    CrowdStrike effectively bricked windows, Mac and Linux today. (possumpat.io)
    submitted 3 months ago by variants@possumpat.io to c/linuxmemes@lemmy.world
    172 comments fedilink hide all child comments
     

    CrowdStrike effectively bricked windows, Mac and Linux today.

    Windows machines won’t boot, and Mac and Linux work is abandoned because all their users are on twitter making memes.

    Incredible work.

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

    Windows didn't do anything, this was an update applied by the Crowdstrike agent.

    [–] peopleproblems@lemmy.world 4 points 3 months ago

    That's the impressive part of all this. Microsoft didn't do it. CloudStrike did it.

    Microsoft left something in a state that allowed CloudStrike to fuck up enough to brick systems.

    It's why we spend a lot of time reviewing security analysis of our own software - if there's a way to fuck everything up, it better not because we enabled it to get fucked.