this post was submitted on 19 Jul 2024
1130 points (96.8% liked)

linuxmemes

21014 readers
731 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
    zephyr
    rtxn
    1130
    IT Department's Plan (i.imgur.com)
    submitted 3 months ago by [email protected] to c/linuxmemes
    114 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 6 points 3 months ago (1 children)

    TBH regardless of windows security, this was clearly the fault of a lack of compatibility. Whether CrowdStrike was made in a way that caused the problem or if the Windows update wasn't properly screened or tested for this kind of failure, I'm sure we'll be hearing a lot about very soon, but the jury is out on which one is at fault.

    [–] PainInTheAES 12 points 3 months ago (1 children)

    Nah, CS sent out a virus definition update that included a driver file that was fucked and caused a boot loop. Because it was a virus definition it bypassed staging rules set by customers. It's 100% on CS unless we want to talk about how Windows architectural choices on how it handles loading improperly formatted kernel level drivers. CS also caused issues on Linux not too long ago.

    [–] [email protected] 1 points 2 months ago* (last edited 2 months ago)

    Why can't we talk about improperly formatted kernel level drivers? MS is notorious for "oops" accidentally rolling drivers back 8 or more years, and now it's become a problem.

    And correct me if I'm wrong but the CS update came before the windows update which caused the problems.

    EDIT: I am a bit off the mark

    On 19 July at 04:09 UTC, CrowdStrike distributed a driver update for its Falcon software for Windows PCs and servers. An update to a configuration file that was responsible for screening named pipes, Channel File 291, caused a logic error with the Windows sensor client, causing affected machines to enter the blue screen of death with the stop code PAGE_FAULT_IN_NONPAGED_AREA, indicating an error caused by a page fault.