this post was submitted on 20 Jul 2024
650 points (98.4% liked)

linuxmemes

21273 readers
1647 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
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] TropicalDingdong@lemmy.world 62 points 3 months ago (20 children)

    Does any one here, working in IT, have a sense for how "on-going" this issue is expected to be? Is this something that is largely going to be resolved in a day or two, or is this going to take weeks/ months?

    [–] MNByChoice@midwest.social 104 points 3 months ago (2 children)

    My guess as a Linux admin in IT.

    I understand the fix takes ~5 minutes per system, must be done in person, and cannot be farmed out to users.

    There are likely conversations about alternatives or mitigations to/for crowdstrike.

    Most things were likely fixed yesterday. (Depending on staffing levels.) Complications could go on for a week. Fallout of various sorts for a month.

    Lawsuits, disaster planning, cyberattacks (targeting crowdstrike companies and those that hastily stopped using it) will go on for months and years.

    The next crowdstrike mistake could happen at any time...

    [–] qjkxbmwvz@startrek.website 48 points 3 months ago (3 children)

    The next crowdstrike mistake could happen at any time...

    Sounds like the tagline to an action movie.

    [–] Agent641@lemmy.world 21 points 3 months ago

    When will crowd strike next?

    [–] MNByChoice@midwest.social 6 points 3 months ago (1 children)
    [–] dumbass@leminal.space 8 points 3 months ago

    You'll be living it soon.

    [–] MadMadBunny@lemmy.ca 2 points 3 months ago

    Coming in a computer near you: Crowdstrikenado!

    [–] Ok_imagination@lemmy.world 21 points 3 months ago (1 children)

    Fully agree as a security engineer with a mostly Microsoft shop. We have some pending laptop fixes, but I think we've talked our cio out of hastily pulling out of CrowdStrike. Really, it didn't hit us hard. Maybe down for 2-3 hours around 4 am Friday morning. Microsoft gives us many more issues more frequently and we don't have constant talk of pulling it out...

    [–] boredsquirrel@slrpnk.net 18 points 3 months ago (1 children)

    Microsoft gives us many more issues more frequently and we don't have constant talk of pulling it out...

    Maybe you should ;)

    As a Linux user I deal with Windows issues way too often administering other laptops.

    [–] Ok_imagination@lemmy.world 5 points 3 months ago
    load more comments (17 replies)