all 5 comments

sorted by: hot top controversial new old
[–] 6 points 2 months ago

I'm starting to think it's time the AUR introduced namespacing packages by the maintainer's AUR username. The single namespace was nice while it lasted, but it seems like we're going to need to get packages based on who's uploading them anyways...

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

    I wonder why Aur is a target.

    You think it's Microsoft related?

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

    Probably because it's an attack vector where the effort required to infiltrate malware is relatively low.

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

    From the mailing list thread:

    For the record, those are all new packages (not orphaned packages being adopted). I assume more will come, we'll clean those as soon as possible.

    In the mean time stay vigilant, probably refrain from installing freshly pushed new packages from the AUR for now.

    Looking over the list it's almost all git/bin versions of files. So they just added a ton of new packages like hexchat-bin that didn't have those versions before and injected malware.

  • source
  • parent
  • [–] 1 point 2 months ago

    I stopped using AUR long before these packages and before the DDOS attacks. Mostly because I started rewriting the code of different applications to compile with QT5 or GTK3. For that I need the source, not what's uploaded on AUR. Which makes me think why I'm still keeping trizen when I don't even use it. 😆

  • source