• roux [he/him, they/them]@hexbear.net
      link
      fedilink
      English
      arrow-up
      11
      ·
      4 months ago

      Is this an issue I’m too Linux-y to understand?

      I used to be way more evangelical about Linux and a few years ago a bash/terminal exploit was discovered after going unnoticed for like a decade that could give someone superuser privileges to a system and my brother and his friend tried giving me shit over it and I was like “yeah, it’s already patched. Like not even an issue. Meanwhile malware and security holes on Windows is just another Tuesday, but whatever.”

      • hello_hello [comrade/them]@hexbear.net
        link
        fedilink
        English
        arrow-up
        12
        ·
        4 months ago

        It’s more GNU than Linux. With proprietary software, people are forced to compete to come up with the quickest solution rather than the most correct. Inevitably under a capitalist system, few large conglomerates dominate the field of technology and bend society to its will leading to a space where only venture capitalist grifters can thrive while the public suffers.

        A monoculture is more vulnerable to being wiped out by a single disease. so in the end, like all problems caused by capitalism, will cause the whole system to collapse.

        It’s not being an “evangelical” which is the lazy excuse that capitalist bootlickers give to any socialist project. It’s about being for the workers.

    • krolden
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      edit-2
      4 months ago

      This has nothing to do with the operating system that was being run and everything g to do with enterprise using a third party monitoring application that was not tested properly before an update was pushed by the vendor

      • PorkrollPosadist [he/him, they/them]@hexbear.net
        link
        fedilink
        English
        arrow-up
        8
        ·
        edit-2
        4 months ago

        It probably doesn’t have much to do with a side by side comparison of the current OS architectures, but there is a lot of historical inertia behind the current state of the Linux and Windows ecosystems. Windows originated as a graphical shell for DOS, which was mainly a single-user, single-process system. Linux originated as a multi-user, multi-process system since inception. Throughout a long period of Windows’s history, these habits lingered among third party developers (developers developers developers) out of convenience or simple necessity for backwards compatibility with other third party components. Even when the NT kernel became the universal Windows kernel with Windows XP, a lot of third party software development adhered to the assumption of a single user machine where the user runs everything with admin privileges. They simply ported their old shit over from (DOS-based) Windows 98/ME and did the bare minimum to make it run on NT. This only reinforced users to run everything as admin, because all sorts of things would break otherwise (admittedly, mostly games and retail shit, but a lot of third-rate enterprise software and harebrained in-house solutions also carried these assumptions forward).

        This has all been pretty much remedied by year 2024, but a lot of these virus scanners and “security” apps still bear the marks of history, running in ring 0 as kernel modules and root-kits to one-up the end-user who is running everything as an admin. The fact that we’re even doing third-party security apps in 2024 is the real failure. This stuff should be (and is, to a large degree) built directly into the OS. This stuff only exists because redundant middle-managers throughout corporate America cannot resist being conned by vendors.