- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
Aqua Nautilus researchers have identified a security issue that arises from the interaction between Ubuntu’s command-not-found package and the snap package repository. While command-not-found serves as a convenient tool for suggesting installations for uninstalled commands, it can be inadvertently manipulated by attackers through the snap repository, leading to deceptive recommendations of malicious packages.
I should maybe have explained one detail better.
It absolutely does. Because the answer for the noobs used to be:
“Just install from your distro’s repo. If you need help, ask others who run your distro about how to do it properly. Do NOT go and just google for something and install it, nor compile from source until you are experienced enough to make an informed choice to do so.” That advice would sidestep so many headaches for noobs and for folks trying to help noobs.
But now that last part is:
“Stay within your distros repos unless you want to use snaps. Of course, if you are going to use snaps, here are these things you should know. You could also probably find a flatpak for many things, so you can try that, but now here’s some things you should know about flatpak. Appimage is also an option, and you can probably find an appimage for some software, but appimage also has some things you should know about how it works and how to integrate it with your system. You should also understand the pros and cons of each of those options with regard to security, and also how that detail compares against just using software from your distro’s repos.”
My eyes glazed over just typing that. That’s not going to help a confused noobie.
A noob shouldn’t have to think about any of this. They would install from gnome software or discover and not know the difference between flatpaks or rpms or debs.