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

linuxmemes

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

    I've found it funny how many people think they need to defend windows by saying " this could've happened to Linux too!!"

    Okay, sure. Yeah you're right about Linux being just as insecure as windows too πŸ˜‰

    [–] proton_lynx@lemmy.world 1 points 3 months ago (2 children)

    I think people are missing the point here. The biggest problem was not that the update was bricking the machines, that could've happened to Linux/macOS/BSD etc. The problem is that the solution to the problem is to MANUALLY access the machine, get into safe mode and type some commands. This is insane. And you should be able to EASILY disable automatic updates for apps like that on Windows Server.

    [–] Buddahriffic@lemmy.world 1 points 3 months ago

    I dunno, I'd say them deploying an update that bricked machines at the scale they did shows they didn't test it very well at smaller scales. They could have even still used their users as beta testers, just needed to do a subset of them first.

    [–] kelargo@lemmy.world 1 points 3 months ago

    Crowdstrike exists for Linux. Are their reports their update affected Linux servers? I have not read that anywhere.

    [–] Psythik@lemmy.world 1 points 3 months ago (2 children)

    Yeah but 14th Gen Intel CPUs are still failing regardless of your OS.

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

    Proudly an AMD user for 25 years now :)

    [–] veni_vedi_veni@lemmy.world 1 points 3 months ago (2 children)
    [–] TrickDacy@lemmy.world 1 points 3 months ago

    not familiar. Their processors tend to last me ~5 years so it's not like I bought every model available

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

    Nobody but the most hardcore AMD enthusiasts used Bulldozer. The 2010s was a tough decade for AMD, to say the least. It wasn't until AM5 came out that I finally switched back to Team Red. Got too used to LGA sockets.

    [–] twei@discuss.tchncs.de 1 points 3 months ago

    I still don't know why they thought sticking with PGA was a good idea... The amount of processors that were ripped out of their sockets is insane

    [–] PainInTheAES@lemmy.world 0 points 3 months ago (2 children)

    Something similar did happen on Linux clients with CrowdStrike installed not too long ago lol

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

    To those many Linux users who took a look at their circumstances and said "I definitely need antivirus software!"

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

    CrowdStrike does more than anti-virus and yes enterprise Linux installations need a lot of security controls that average Linux users don't need.

    [–] TrickDacy@lemmy.world -1 points 3 months ago (1 children)

    Ok fine simps, Linux is exactly as shitty as windows this was totally only a coincidence

    [–] PainInTheAES@lemmy.world 1 points 3 months ago

    Bruh, I've used Linux for over 10 years. I run Arch on my laptop and have a homelab powered by Proxmox, Debian, and OPNSense. I don't run any AV in my lab but do follow other security practices.

    At work it's a different story. Products like CrowdStrike also collect logs, scan for vulnerabilities, provide graphing and dashboarding capabilities, provide integrations into ticketing platforms for investigation and remediation by security teams, and more. AV is often required because Windows users can upload infected files to Linux-run SMB shares. Products like CrowdStrike often satisfy requirements set by cybersecurity insurance.

    This is not simping, this is not Linux vs Windows. You just clearly have no experience in the enterprise Linux space and business security requirements.

    [–] MartianFox@lemmy.ml 0 points 3 months ago (2 children)

    Sounds a bit like its a bad idea to install CrowdStrike regardless of the system πŸ™ƒ

    [–] cerement@slrpnk.net 1 points 3 months ago

    checkbox compliance – companies are required to have something in place that checks the box so they can pass the audit

    [–] jaybone@lemmy.world 0 points 3 months ago (1 children)

    lol yeah that’s a glowing review.

    β€œOh, we can fuck other shit up too!”

    [–] TrickDacy@lemmy.world 0 points 3 months ago (1 children)
    [–] madcaesar@lemmy.world 1 points 3 months ago (1 children)

    Noone needs to defend Windows. We need to defend the truth. And the truth is that this was not a Windows issue. It's a Crowdstrike issue.

    [–] TrickDacy@lemmy.world 0 points 3 months ago (1 children)

    Windows being an insecure shit show is no one else's fault though. Not sure why that draws an argument. It's well known

    [–] madcaesar@lemmy.world 0 points 3 months ago (1 children)

    True. But nothing to do with this incident. That's the point.

    [–] TrickDacy@lemmy.world 0 points 3 months ago (1 children)

    Everything to do with it. You don't buy expensive software to protect your shitty OS unless it's a shitty OS

    [–] madcaesar@lemmy.world 0 points 3 months ago (1 children)

    Linux had a similar outage a few weeks ago, my man.

    [–] TrickDacy@lemmy.world -1 points 3 months ago

    And yet I heard zero peeps about it. Probably because 99% of IT departments know windows is vulnerable as fuck while 99% know that Linux doesn't need babysitting.

    "It's technically possible for other OSes to be affected by a thing like this" is a shit argument and you should get the MS dick out of your mouth.