red_giant [comrade/them, he/him]

  • 1 Post
  • 3 Comments
Joined 7 months ago
cake
Cake day: January 11th, 2026

help-circle


  • Shutting down AUR is a legit option for sure but it’s not convincing it would solve much.

    You can always just not install packages from AUR if you’d prefer to be immune to the threat.

    Debian is beginning to enforce reproducible builds which is a great step. Requiring source repos to use signed commits would be another.

    Supply chain attacks is not a problem that can be erased but the idea that I cannot install a patch for a critical vulnerability because I’m waiting for community-review seems extreme as well. And who is to say that community review is immune to hijacking anyway?

    If you want professionally vetted code and you also want a library of installable packages then really you want Mac OS and the Mac App Store.


  • Review costs money and is slow, meaning vulnerabilities that already exist persist for longer before being patched.

    This is a real double-edged sword for open source. FOSS as a software supply chain relies on trust and identity.

    Review doesn’t fix this problem. You can increase security of incoming code at the expense of decreasing security of existing code by virtue of slowing down the response-time to existing security threats. The social architecture of code distribution is the vulnerability here.

    Ultimately, arch can’t take ownership of all the code that is possible to install on arch.

    AUR makes it clear that packages there are not vetted. You’re trusting the developer and the developers security practices.