this post was submitted on 03 Aug 2026
17 points (100.0% liked)

Arch Linux

9896 readers
1 users here now

The beloved lightweight distro

founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Strit@lemmy.linuxuserspace.show 4 points 4 days ago (1 children)

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.

[–] victorz@lemmy.world 1 points 4 days ago (1 children)

You never ever install a -bin package from the AUR?

[–] Strit@lemmy.linuxuserspace.show 2 points 4 days ago (1 children)

Rarely, but I check the PKGBUILD to see if the binary is what I expect it to be.

[–] victorz@lemmy.world 1 points 4 days ago* (last edited 4 days ago) (1 children)

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 3 points 4 days ago (1 children)

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).

[–] victorz@lemmy.world 1 points 4 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. 😅