• CrazyLikeGollum@lemmy.worldEnglish
        0·
        2 months ago

        Oh no, you misunderstand. I support a Unix system. Not Linux, not BSD, not Solaris. Y2K will be a problem in 2029 if don’t remember to set the clock back. Assuming the PDP-11 still works by then.

        • bamboo@lemmy.blahaj.zoneOPEnglish
          0·
          2 months ago

          Does it not have epoch set to 1970-01-01 00:00:00? Or does the PDP-11 only use a non power of 2 number of bits, and you’ve already set the clock back before? Genuinely curious, never heard of 2029 problem before.

          • CrazyLikeGollum@lemmy.worldEnglish
            0·
            2 months ago

            Not a 2029 problem, maybe could have been clearer there. The clock is set 30 years behind. So, the clock will roll over to the year 2000 in 2030, meaning it will be a problem to address in 2029.

  • JJROKCZ@lemmy.world
    0·
    2 months ago

    If only our vendors made Linux versions of their systems and regulators would approve them or the OS but no, my regulators only allow windows and approved software that they verify the hashes of every few months for changes

    • Marduk73@sh.itjust.works
      0·
      2 months ago

      I laugh and it does/did(over now) affect me. Bwahaha. Im getting work done and nobody can interrupt with email.

      • jj4211@lemmy.world
        0·
        2 months ago

        All I’ve noticed is that a lot of internet related things in my work are much faster today.

        The schadenfreude could only be sweeter if my company used CrowdStrike on all the Windows systems. Then I really would have had a very peaceful focused day.

    • marcos@lemmy.world
      0·
      2 months ago

      Remember guys, it took about a decade for Solar Winds to discover somebody had root access to everybody that used their software, another decade for somebody outside Solar Winds to discover it and tell everybody, and half a decade with nobody claiming to have solved the issue up to now.

      So when you believe that your computer with an EDS is safe just because you can’t use it, think again.

    • cordlesslamp@lemmy.today
      0·
      2 months ago

      Reminds me of a local cyber security firm, which declares war on a group of hackers. The CEO went on television to “double dog dare” the hackers to hack their servers and claim their firewalls are impenetrable.

      Well you can guess the results, within 48 hours, their servers went down one after another. And when shit about to hit the fan, they literally turned off all of their servers for days. They hired a 3rd party IT firm to patch their security, then the CEO declared victory in a local newspaper.

    • lobut@lemmy.ca
      0·
      2 months ago

      The most secure computer is the one not running any software. That’s why I recommend Crowdstrike.

    • explodicle@sh.itjust.worksEnglish
      0·
      2 months ago

      He’ll just get fired, apply somewhere else, and they’ll only know the dates he worked at CrowdStrike.

      If anybody cared, they would have switched away from M$ by now.

    • Robin@lemmy.worldEnglish
      0·
      2 months ago

      For a company this big it would also have to have gotten past a code review and QA team, right? … right? …

      • merc@sh.itjust.works
        0·
        2 months ago

        Code review, QA team, hours of being baked on an internal test network, incremental exponential roll out to the world, starting slow so that any problems can be immediately rolled back. If they didn’t have those basics, they have no business being a tech company, let alone a security company who puts out windows drivers.

        • yrmp@lemmy.world
          0·
          2 months ago

          We do.

          “If something goes down over the weekend, fewer people see it” - my leadership team.

          I guess Asia can report the problem on Sunday and I’ll get a nastygram and fix it that afternoon.

    • qjkxbmwvz@startrek.website
      0·
      2 months ago

      Yeah, something this big is absolutely not one engineer’s fault. Even if that engineer maliciously pushed an update, it’s not their fault — it was a complete failure of the organization, and one person having the ability to wreck havoc like this is the failure.

      And I actually have some amount of hope that, in this case, it is being recognized as such.

        • merc@sh.itjust.works
          0·
          2 months ago

          No they won’t, not if they’re in the slightest bit competent.

          Blameless post-mortem culture is very common at big IT organizations. For a fuck-up this size, there are going to be dozens of problems identified, from bad QA processes, to bad code review processes, to bad documentation, to bad corner cases in tools.

          There will probably be some guy (or gal) who pushed the button, but unless what that person did was utterly reckless (like pushing an update while high or drunk, or pushing a change then turning off her phone and going dark, or whatever) the person who pushed the button will probably be a legend to their peers. Even if they made a big mistake, if they followed standard procedures while doing it, almost everyone will recognize they’re not at fault, they just got to be the unlucky person who pushed the button this time.

  • Justin@lemmy.jlh.nameEnglish
    0·
    2 months ago

    The fact that random companies like Crowdstrike have kernel drivers in millions of computers they they ship remotely is a security risk in and of itself. We’re lucky crowdstrike just shipped a bug that crashes computers, other companies could have shipped a lot worse.

  • CileTheSane@lemmy.ca
    0·
    2 months ago

    Also: don’t trust your employees to boot into safe mode.
    Trust a 3rd party to freely install system level files at any time.

    I knew how to fix the computers at work today in the morning, but we couldn’t get through to the help desk to get the bit locker codes for each computer until near the end of the day.

    • cqst@lemmy.blahaj.zone
      0·
      2 months ago

      Also: don’t trust your employees to boot into safe mode. Trust a 3rd party to freely install system level files at any time.

      Exactly. This is exactly the problem, and unless people wisen up the software security problem is only going to get worse. Companies and Governments need to rethink how they approach security entirely. This is a preview of what is to come, its only going to get worse and more damaging from here, and none of the vendors care.

      • uis@lemm.ee
        0·
        2 months ago

        Companies and Governments need to rethink how they approach security entirely. This is a preview of what is to come, its only going to get worse and more damaging from here, and none of the vendors care.

        It is easy one for goverments. Ban security through obscurity. As well proprietary security software.

        Moonbutt’s moonbuck))) Have I seen you somewhere?

        • cqst@lemmy.blahaj.zone
          0·
          2 months ago

          Ban security through obscurity. As well proprietary security software.

          The government likes proprietary software. They are never going to ban it.