top 50 comments

sorted by: hot top controversial new old
[–] 29 points 2 months ago (19 children)

Adoptions are a mistake anyways. Remove unmaintained packages and block the name for several months.

  • source
  • hideshow 19 child comments
  • [–] 42 points 2 months ago (13 children)

    Adoption of unmaintained packages to maintain them is not a mistake. The problem is the current implementation, not the idea behind it. It's like saying the AUR is a mistake, because some people do malicious stuff.

    They should find a better solution, like adoption shouldn't be granted to everyone without question, especially new accounts who didn't maintain anything before. Mass adoption shouldn't be granted automatically (limit rate), in example 1 package adoption per day and if someone wants more, admins or moderators need to approve. And updates of newly adopted packages should wait a day.

    Also the AUR helpers should do a better job. Always ask if a new adopted package should be updated and give a warning the maintainer changed.

  • source
  • parent
  • hideshow 13 child comments
  • [–] 13 points 2 months ago (3 children)

    The problem is the current implementation

    Yes, exactly this! I am not surprised it happens. I’m surprised it didn’t happen before.

    especially new accounts

    Weren’t there “sleeper accounts” registered years ago that became active in the current wave?

    Also the AUR helpers should do a better job.

    Even experienced people will just update as if nothing could happen. Adopted packages should have to use a different name and the current name being blocked so it WILL get attention when some tries to update their system.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 5 points 2 months ago* (2 children)

    Weren’t there “sleeper accounts” registered years ago that became active in the current wave?

    Which does not invalidate my point about new accounts, but yes. Its important for new accounts, so once a sleeper account is banned, its not that easy to just create thousands of new accounts while everyone is focusing on the current active ones. And if, as I suggested, mass adoption per account is not possible, then the attacker has less to attack.

    Edit: They need to make sure that sudden editing many packages in short time, with probably the same or similar lines should be automatically reported. They need some automated checks in place, at the very least. This would be a very suspicious behavior if many accounts are not active, and then suddenly all of them do something.

    Even experienced people will just update as if nothing could happen.

    Then you can't fault the system, if you are this reckless.

    Adopted packages should have to use a different name and the current name being blocked so it WILL get attention when some tries to update their system.

    This would break all dependencies of this package. The point of adoption is to keep it working and stable. I'm highly against force changing the name, that is not a solution (at least not one I am happy about).

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 2 months ago (1 child)

    [Changing a package’s name] would break all dependencies of this package.

    Yes, that is correct. But that should not be a big deal for packages that are actively maintained. The maintainer can simply change the dependency to the new name after making sure the new package is legit.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 2 months ago*

    OK, that's a good point. It would prevent auto updating. However any package that is NOT updated, should stay with same name in my opinion. So that everything (with the old secure code) stays intact and working. The name change should be part of the the update process. So it only breaks if you want to update, which would ensure compatibility if you choose not to (as it is safe). Something along the likes like this. I agree with your suggestion now, because that seems to be sensible idea.

  • source
  • parent
  • load more comments (8 replies)
  • [–] 13 points 2 months ago (3 children)

    Remove unmaintained packages and block the name for several months.

    Alright, but that would mean most of AUR. Have a look at the package statistics box on the AUR homepage. Most packages fall under that definition in one way or another. The vast majority of the AUR is package some random person added once then never bothered with ever again.

    Frankly I'm surprised that the AUR has survived for so long in its current form, for what is basically a shell script distribution system with zero supervision and zero safety guards.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 2 months ago (2 children)

    The vast majority of the AUR is package some random person added once then never bothered with ever again.

    Yes, that sucks. But I was thinking of exclusively this packages: https://aur.archlinux.org/packages?submit=Orphans

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (1 reply)
    [–] 11 points 2 months ago* (last edited 2 months ago) (14 children)

    I use malware, btw 😎

    Arch should be stopped to be recommended to new users of Linux ASAP

  • source
  • hideshow 14 child comments
  • [–] 9 points 2 months ago (6 children)

    Is anybody really recommending Arch to new users though?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 10 points 2 months ago (4 children)

    Yeah, there's a ton of people that recommend Cachy when it is really meant for tinkerers IMHO

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 2 months ago (2 children)

    I'm very tired of the rhetoric that Arch is only meant for tinkerers. If all you do is have plasma steam and a web browser it's no more or less likely to break than any other distro. You could go your entire life without ever looking at the terminal.

    And while yes this malware is a problem it is specifically in the aur, the arch user repository an unofficial repository not officially supported, just don't use it. Unless you need a weird piece of software generally related to some type of specific hobby you're unlikely to ever even want to look at it anyway.

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (2 replies)
  • load more comments (1 reply)
  • [–] 2 points 2 months ago (2 children)

    Arch as far as I am aware has never been recommended to new users. Sure their is CachyOS and other variants. And on top of that AUR you shut read the build scripts. But I suppose not many people do that unfortunately.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 months ago

    more importantly, they don't recommend that users use the AUR repository (that isn't to say they are opposed to it). Some advice they have given is to review what the dependencies are before executing the package with an AUR helper or manually.

    Just to make a point, there is a surplus of these non officially supported (from OS developers) repositories, such as the terra repository for fedora. It has the same vulnerability as AUR, and yet that is targeted for new users.

    Much like how fedora doesn't officially support Terra, arch doesn't support AUR. There is a reason why it's called AUR (arch user repository) over ASR (arch supported repository). AUR entails that it is not supported by arch.

  • source
  • parent
  • load more comments (1 reply)
  • load more comments (3 replies)
    [–] 8 points 2 months ago

    Why tf didn't they leave it disabled since the last attack?

  • source
  • [–] 7 points 2 months ago (2 children)

    Just saw DeepSeek TUI in there, that's probably going to be a whopper that hit quite a few users.

  • source
  • hideshow 2 child comments
  • [–] 12 points 2 months ago* (last edited 2 months ago) (1 child)

    You mean https://aur.archlinux.org/packages/deepseek-tui-git from the list https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/thread/P4WIRHTFNH2YZWQHGBAKQWX5YOAFIDLY/ ? It has 0 votes and Popularity is at 0.000000, since it was uploaded 2 months ago. And there is a non Git version that is not listed (probably not affected) at https://aur.archlinux.org/packages/deepseek-tui . On top of it, on their website https://deepseek-tui.org/#install the main recommended way to install it is with npm and there is even a way to build it with Rust it seems (I'm a bit unsure).

    So I don't think it hit that many users, as only a couple of people since Mai would want to install it, and they have to have updated it to build from source in recent days. That is a very narrow number of people, just by my gut feeling.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 2 months ago* (1 child)

    Do I really need to audit my system again?

  • source
  • hideshow 1 child comment
  • [–] 12 points 2 months ago

    Not if you follow the normal safety precautions for using the AUR. There are several things you can do to look for red flags, but the most essential thing is to read the PKGBUILDs. And helpers like yay, paru and Shelly can all show diffs which makes that much easier after the initial installation because in most cases you'll just see that the version and checksum has changed which means it's as trustworthy as last time.

    This has always been the case, and will continue to be the case unless the Arch team restricts the AUR which quickly can make it lose exactly what makes it so good.

  • source
  • parent
  • [–] 4 points 2 months ago (10 children)

    friends don't let friends use the AUR

  • source
  • hideshow 10 child comments
  • [–] 2 points 2 months ago (6 children)
  • load more comments (2 replies)
  • load more comments (3 replies)
    [–] 3 points 2 months ago (5 children)

    Man I feel like I dodged a bullet switching to Fedora right before this AUR fuckery started to happen...

  • source
  • hideshow 5 child comments
  • [–] 12 points 2 months ago (3 children)

    You don't have to use AUR to use Arch. Just like PPA for Ubuntu or Fedora's Copr.

  • source
  • parent
  • hideshow 3 child comments
  • load more comments (1 reply)
  • [–] 3 points 2 months ago

    I feel like when this pops up everyone freaks out and yells about how it's proof the aur sucks and arch is doomed. Do you people randomly install GitHub repos without any due diligence? Do you click on random ads to download bake bean can cursors? There's malware fuckin everywhere. Just do your due diligence and don't get screwed. And if you do get malware, have a plan to make it irrelevant. Anyone who doesn't do these things should in no way be using the AUR.

  • source
  • load more comments
    view more: next ›