• Strit@lemmy.linuxuserspace.show
    link
    fedilink
    arrow-up
    0
    ·
    7 days ago

    But if you read the PKGBUILD, you would see that it downloads and runs a black-box binary and should therefore not install it. It’s a little harder with PPAs I think. The build files are not so easily found.

        • Victor@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          7 days ago

          Yet, to quote:

          But if you read the PKGBUILD, you would see that it downloads and runs a black-box binary and should therefore not install it.

          • Strit@lemmy.linuxuserspace.show
            link
            fedilink
            arrow-up
            0
            ·
            7 days ago

            And you can check the shasum of the binary to see if it actually matches that provided by the developers of the application.

            A malicious PKGBUILD, which is what is being talked about, you would see that it downloads a binary that does not come from the developers and so you should not install that.

            If the attack happens on the developers repo, not even Linux repository packages would be safe at that point (eg, the xz heist).

            • Victor@lemmy.world
              link
              fedilink
              arrow-up
              0
              ·
              7 days ago

              If the attack happens on the developers repo, not even Linux repository packages would be safe at that point

              I figured this is the type of attack you were referring to, but then you say you yourself don’t really live by that safety measure.

              I don’t either. I don’t have enough time, patience, or knowledge to check the source of everything I install to see if it suddenly has malware. That’s where I draw my line in the security sand. 😅