• Possibly linux@lemmy.zipEnglish
    83·
    3 hours ago

    Is this news worthy? X is the classic example of how a code base becomes completely unmanageable

  • exu@feditown.comEnglish
    21·
    4 hours ago

    I know Phoronix comments, but what’s up with the Linux Mint hate?

  • d_k_bo@feddit.orgEnglish
    16·
    3 hours ago

    By providing a modified bitmap to the X.Org Server, a heap-based buffer overflow privilege escalation can occur.

    Maybe we should stop writing security critical software in memory unsafe languages. I now this vulnerability was introduced a long time ago, but given that major Wayland compositors are still written in C, something like this isn’t too unlikely to happen again.

    • leo85811nardo@lemmy.worldEnglish
      4·
      2 hours ago

      Wait till bro find out the program written in the “memory safe language” depends on many libraries written in C

    • superkret@feddit.orgEnglish
      11·
      2 hours ago

      Let’s re-write all currently existing software in Rust, then there will be no more security holes, and every computer will be safe forever.

    • woelkchen@lemmy.worldEnglish
      3·
      2 hours ago

      major Wayland compositors are still written in C

      KWin is written in C++ but yes, it’s not a “safe” language.

      something like this isn’t too unlikely to happen again.

      With at least three mainstream implementations – KWin, Mutter, and wlroots – it’s highly unlikely that all would ever be equally affected by one bug.