• Septimaeus@infosec.pub
      link
      fedilink
      English
      arrow-up
      9
      ·
      edit-2
      4 hours ago

      Upvoting both comments for awareness, since Linux is the first of a multi-step process, not a privacy panacea.

      But we must be clear that in both theory and practice there’s little comparison between systemd and modern Windows machine-user association.

      Someone using Windows regularly has a gaping wound, is actively bleeding out. Switching to Linux is just a tourniquet, but every other treatment is at best no-effect until that tourniquet is applied.

      E: transpose systemd/Windows for clarity

      • DevDave@piefed.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 hours ago

        Also as a life long programmer, I have this feeling it is possible to just go in and make some changes so I can have the system just make shit up about the TPM while indeed also doing the equivalent of having system-d decide to respond with random bullshit.

        Don’t even need to be a programmer, just find a community of them that you trust that distribute their own “fixes”.

        Definitely not doing that with anything else because its both hidden in compilation and buried like herpes across multiple components. Probably/hopefully not directly related but I really want to know what they changed to break the clipboard service.

        • Septimaeus@infosec.pub
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 hours ago

          And you’d be technically correct, the best kind of correct.

          To the inquisitor:

          any distro that’s fully OSS can be fully compiled from scratch with any modifications you choose).

          Though yes, if you’re still using Windows, the learning curve may look like a wall.

          I really want to know what they changed to break the clipboard service

          Guessing the X11 [X]Wayland migration KDE Plasma bug report? Should be fixed in 6.5.2.

        • Septimaeus@infosec.pub
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          4 hours ago

          I’m specifically highlighting that there is none though I acknowledge machine ID makes it easier.

          ETA: edited original comment to be more clear

    • mic_check_one_two@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      3
      ·
      3 hours ago

      Yeah, motherboard-level tracking is scary because even the OS won’t be able to detect it. The truly paranoid people (and security researchers) go as far as desoldering chips to ensure nothing phones home.