If it's endorsed by the project team I might as well. At that point it's the same as downloading from GitHub and if I am in AUR I've probably not found it in standard repos nor flathub.
I use Arch without touching this AUR in my latest install. Just use what's in the main package repos or flathub
I just don’t understand the process of I don’t have two minutes to read what I’m installing. It’s fucking batshit crazy that all these retards want to come use Linux which is fine but then when they get solid advice they tell us they can’t be bothered.
Yeah, when something isn't in the official repos, NixOS exists, Flatpak exists, and they're all vetted.
Wanting a super clean system where everything is managed by pacman is purely about taste, so if you want it, you clearly can be bothered to put in the 2 minutes of work.
its
I was contemplating moving to NixOS, but then another fiasco just happened, masse me question what would one have to lose by switching to Qubes instead, considering the increasingly surveiling internet.
Nah, if you really want to live on the bleeding edge you gotta make blindly installing vibecoded junk from shady parts of the AUR part of your workflow
STABLE IS FOR HORSES I LOVE GAMBLING
/s
I wish I could give you a second upvote, that's hilarious 😂
I once found a Rust program that streamlined the PKGBUILD reviewing process a lot by, first of all, giving you a really neat list of patterns and behaviours that would make a PKGBUILD suspicios or even plain dangerous, then having a scriptable rule-based engine that would either abort that operation, or show warns and workarounds to you.
I forgot its name, unfortunately, and I installed it on my previous installation (Garuda, now I'm on CachyOS).
Very dumb of my part not to try to write that down before the OS change lol.
pkgwatch maybe?
It was not that one, but yeah, it's basically the same.
I just remembered the one(s) I used a while ago, tho, they were aur-guard, and aur-scanner, I used these two (the second one just because its aur-scan codes [OPTIONS] and aur-scan explain <CODE> commands.
All pointing with fingers to AUR, but the issue was (yet again) with NPM.
Sorry I missed something, how so?
The compromised packages load a script from thr net that runs a compromised npm package ("atomic-lockfile" 1.4.2).
Ok, also a AUR issue. But more so a NPM one, since they have all full moon two supply-chain attacks.

If you want a bunch of stuff that's not in core or extra and you don't want to intensely babysit the AUR, you could try Chaotic-AUR. It hosts prebuilt packages for a bunch of AUR packages which are actively maintained by the Chaotic team.
I consider it to be more secure than the AUR proper since they actually care for their packages and review nontrivial changes. For instance, the recent takeover attacks didn't hit Chaotic-AUR builds since the changed packages didn't make it past the review.
It's still an unofficial third-party repository and closer to the AUR than to extra but I consider it a major step up.
I just recently reinstalled since I didn't feel comfortable with how many AUR packages I had and ive been using ChaoticAUR exclusively now. Can confirm that its a great repo
Yes, but is it good, neutral, or evil?

I mean how often do you install AUR packages? Usually takes like a minute or so to skim through PKGbuild and the pkg comments and look for obvious issues. And most updates are just a sha hash and version change, taking like 5s to check.
Rarely, to be sure. I tried Arch for a bit, but I need a computer that I can actually use to get shit done, that isn't a constant project itself. Even Qubes doesn't require as much effort to keep operational.
But wasn't the latest AUR attack from a dependancy in the pkgbuild? Going out of your way to review all the dependencies as well is not really possible by just skimming through the script.
I need a better wrapper that shows me diffs since last build. I’m too lazy for this
Also pulling in release messages from git etc would be nice
paru
AUR Arch UrGettingMalware Repository
just use nix instead
we have super secure mechanisms in place to prevent supply chain attacks
/s (nix just hasn't been targeted yet (as far as we know 💀💀))
/s (nix just hasn’t been targeted yet (as far as we know 💀💀))
Isn't the real security through obscurity just being such a fringe market no one bothers? 🤔
just use nix instead
Maslow, is this your hammer?
Yeah, I just update all 20 flakes that I sourced from github and pray that none of them were hacked
Update your desktop only all one or two weeks, get basic protection (adblocker, hosts file), read the news.
It's a peaceful life.
I'm running Arch daily since 2015, was on Debian before. I install and try a lot of stuff. Never had anything bad happened to me once. Worst case scenario the shit I just installed didn't work so I have to debug it.
Not endorsing this apparently dangerous lifestyle, but also a little bit maybe
Yeah same. Aur has been significantly less virus prone than the windows norm (inb4 wut abut winget >;ppp) of "Googling some shit you want and clicking the first website to roll the dice on predatory ads or malware or maybe the thing you wanted"
...not to mention if you have btrfs you can just rollback a month or two and call it a day.
This is more important after the recent news of malware on AUR
Someone put my WM on the AUR. I am thus proud to be authoring malware :)
I usually do, but I don't really know what I should be looking for. What are some red flags?
I don't mean this in any mean way, but if you don't know what you should be looking for, you probably shouldn't install AUR packages. Just as I wouldn't recommend someone who has never climbed a mountain to try mt everest.
You need to be able to understand the build process before you install anything from the AUR. Everything else is the equivalent of installing random exe's you found on a forum on windows.
Luckily, there's a lot of different videos online regarding the AUR build process, and the archwiki has an excellent article aswell.
To be clear, I have like... three? extremely popular AURs installed - I'm definitely not in the habit of grabbing random stuff.
Check the list of dependencies. If you really want to vet the package, look through all of the dependencies listed and read their package descriptions on their source page (github, gitlab, codeberg, whathaveyou). Check also the URL, from which makepkg (or yay or whatever) is going to pull some of the data. Is the URL legit?
PKGBUILD of localsend
# Maintainer: NourEddineX
# Contributor: Nixuge
# Contributor: Noah Vogt <noah@noahvogt.com>
# Contributor: SpieringsAE (aarch64 addition)
# Note:
# using the .deb instead of the .tar.gz as it already contains the icons as well as the .desktop file.
pkgname=localsend-bin
pkgver=1.18.0
pkgrel=1
pkgdesc='An open source cross-platform alternative to AirDrop'
LOOK HERE
url=https://github.com/localsend/LOCALSEND
LOOK HERE
arch=('x86_64' 'aarch64')
license=(Apache-2.0)
LOOK HERE
depends=(fuse2 xdg-user-dirs libayatana-appindicator)
LOOK HERE
conflicts=('localsend')
provides=('localsend')
options=(!debug)
source_x86_64=("${url}/releases/download/v${pkgver}/LocalSend-${pkgver}-linux-x86-64.deb")
source_aarch64=("${url}/releases/download/v${pkgver}/LocalSend-${pkgver}-linux-arm-64.deb")
sha256sums_x86_64=('dae68192ad43a59a68df06454eb5fa4e9a9f86a343fe430165efd8b18863d0f4')
sha256sums_aarch64=('eb24e724fbdf830c8fb07dfc66b76b8a649923d083278305a63d5d539db4b606')
_pkgdesktop="localsend_app.desktop"
prepare() {
tar -xf data.tar.zst
}
build() {
sed -i -E \
"s|Exec=localsend_app|Exec=localsend|" \
"${srcdir}/usr/share/applications/${_pkgdesktop}"
# Adjust .desktop to have it point to the correct icon
sed -i -E 's/^Icon=.+/Icon=localsend/' "${srcdir}/usr/share/applications/${_pkgdesktop}"
}
package() {
# Desktop
install -Dm644 "${srcdir}/usr/share/applications/${_pkgdesktop}" "${pkgdir}/usr/share/applications/${pkgname%-*}.desktop"
# Icons
install -dm644 "${pkgdir}/usr/share/icons/"
cp -a "${srcdir}/usr/share/icons" "${pkgdir}/usr/share"
# Dirty - rename icons to localsend
for res in "128x128" "256x256"; do
mv "${pkgdir}/usr/share/icons/hicolor/${res}/apps/localsend_app.png" "${pkgdir}/usr/share/icons/hicolor/${res}/apps/localsend.png"
done
# Executable
install -dm755 "${pkgdir}/opt/${pkgname%-*}/"
cp -a "${srcdir}/opt/localsend_app/." "${pkgdir}/opt/${pkgname%-*}"
# Same as icons - rename to localsend
mv "${pkgdir}/opt/${pkgname%-*}/localsend_app" "${pkgdir}/opt/${pkgname%-*}/localsend"
# Symlink executable
install -dm755 "${pkgdir}/usr/bin"
ln -s \
"/opt/${pkgname%-*}/${pkgname%-*}" \
"${pkgdir}/usr/bin/${pkgname%-*}"
}
Yeah. There's also some others behaviours to look at. Like, does the PKGBUILD install the package on some non-standard location? That's a suspicious behaviour, although it's not an automatic red flag by itself. Does it execute arbitrary code or any external script (worse if it's Python, Lua or JS)? That's a HUGE red flag in most of cases. Does it (ab)uses of AWK, sed and the like? That's also suspicious in a variety of cases.
as the other commenter said, but worth echoing:
- is it suddenly using npm to install/run something? (iirc this was the attack vector for most packages that were infected)
- suddenly added some weird extra wget/curl/whatever to packaging methods to fetch something weird?
- are the package's sources (eg. github urls) legit?
Generally you should be aware of who'se software you're installing -> check if it's downloading the stuff from right place, and nothing extra. The PKGBUILD changes in the aur website are pretty good indicator if something has changed and how.
edit: npm itself, or it's usage isn't bad - but it is quite suspicious if the AUR package isn't for some webapp or so.
without reading [it is] pkgbuild
I didn't know it was.
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
5. 🇬🇧 Language/язык/Sprache
- This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.