Earlier quoted context omitted.
No, what I am referring to is that they show me a captcha page that they have ripped off from cloudflare.
It is shockingly similar looking. At first I thought they were on an expensive enough Cloudflare plan to remove branding. But 1. the site owner has beef with Cloudflare and 2. Cloudflare doesn't use recaptcha anymore so it does just seem like a very similar theme (IDK if it was actually copied or not, it is not that complex of a design).
Installing Every Arch Package
81–90 of 90 posts
Re: Installing Every Arch Package
#82Earlier quoted context omitted.
No, what I am referring to is that they show me a captcha page that they have ripped off from cloudflare.
It is shockingly similar looking. At first I thought they were on an expensive enough Cloudflare plan to remove branding. But 1. the site owner has beef with Cloudflare and 2. Cloudflare doesn't use recaptcha anymore so it does just seem like a very similar theme (IDK if it was actually copied or not, it is not that complex of a design).
Re: Installing Every Arch Package
#83Earlier quoted context omitted.
The unofficial ones are ~40 lines of shell script that generally start by pulling down a VCS repo or tarball from somewhere. They check the checksum of tarballs, but if you’re pulling from the AUR you’re trusting not just the ~40 lines but also the much larger body of code that’s getting fetched.
No package maintainer is verifying the code of every update of the software they're packaging. Those 40 lines of shell script are the only relevant difference between packages and the AUR, security wise.
As for the security review, I’d agree that no maintainer is verifying the code in every update of the software they’re packaging. This doesn’t mean that, as implied in the comment I replied to, you only have to review the 40 lines. It means that you’re accepting risk or accepting workload in either case (or both!), depending on how deep you look into the supply chain.
Re: Installing Every Arch Package
#84Earlier quoted context omitted.
No package maintainer is verifying the code of every update of the software they're packaging. Those 40 lines of shell script are the only relevant difference between packages and the AUR, security wise.
In the core repos, those 40 lines still exist. The AUR and core repos use the same PKGBUILD scripts. So the shell script isn’t a difference between core and AUR packages. As for the security review, I’d agree that no maintainer is verifying the code in every update of the software they’re packaging. This doesn’t mean that, as implied in the comment I replied to, you only have to review the 40 lines. It means that you…
I agree with the rest, I'm really talking more about the comparative risk from AUR compared to the repos. The real danger is that someone snuck something malicious in the PKGBUILD and that no one noticed yet. Other than that, the threat is the same as using the repos, assuming you trust the maintainers, which is IMO a reasonable assumption if you're already using it as your distro.
Re: Installing Every Arch Package
#85For some reason I feel bad downloading too many unnecessary packages from these volunteer projects. I guess any given mirror must have enough users that even something like this is just a raindrop in the ocean, though?
[1] This is n=1 data because I can only speak for my own machine, so obviously take this with a grain of salt.
Re: Installing Every Arch Package
#86Copying my comment from reddit[0]: For clarity, Arch has about 10k packages, AUR has around 60k packages. I believe this post is "just" about the 10k. > I’d like to see someone do this for Ubuntu, Debian, and NixOS and watch them suffer. Speaking for NixOS: I have. I would sometimes do a nixpkgs-review[1] of the mass "rebuild" PRs for Nixpkgs[2]. Hard to know how long it took to build as I would just let it "cook" on…
Nix has been behaving that way for at least 8 years: https://github.com/NixOS/nix/issues/308
Re: Installing Every Arch Package
#87Copying my comment from reddit[0]: For clarity, Arch has about 10k packages, AUR has around 60k packages. I believe this post is "just" about the 10k. > I’d like to see someone do this for Ubuntu, Debian, and NixOS and watch them suffer. Speaking for NixOS: I have. I would sometimes do a nixpkgs-review[1] of the mass "rebuild" PRs for Nixpkgs[2]. Hard to know how long it took to build as I would just let it "cook" on…
Installing every single Nix package is a piece of cake. Just run nix-env -i without argument. Nix has been behaving that way for at least 8 years: https://github.com/NixOS/nix/issues/308
Re: Installing Every Arch Package
#88Now install every AUR package. Bonus points for heuristically looking for cryptominers after it's done.
Installing every Arch/AUR package could break some hardware compatibility which we've taken for granted(Story link is not opening as of writing, So not sure whether this case has been covered in it).
[1] https://unix.stackexchange.com/questions/670636/unable-to-us...
Re: Installing Every Arch Package
#89Re: Installing Every Arch Package
#90Earlier quoted context omitted.
It's only a matter of time. Linux really only has a good malware track record due to lack of popularity.
It seems like the popularity on servers would increase the likelihood.
It's basically unnecessary to run any sort of anti-malware program on Linux, because not enough people use it for writing viruses for it to be profitable. And because the people who use it as a desktop are generally more knowledgeable and safe with their habits.