A community for everything relating to the GNU/Linux operating system
Also check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
Yeah I hate this stuff too, I usually pipe it into a file figure out what it's doing and manually install the program from there.
FWIW I've never found anything malicious from these scripts but my internal dialogue starts screaming when I see these in the wild, I don't want to run some script and not know what it's touching malicious or not it's a PITA.
As a linux user, I like to know what's happening under the hood as best I can and these scripts go against that
| sh stands for shake head at bad practices
You could just read the script file first.. Or YOLO trust it like you trust any file downloaded from a relatively safe source.. At least you can read a script.
For security reasons, I review every line of code before it’s executed on my machine.
Before I die, I hope to take my ‘93 dell optiplex out of its box and finally see what this whole internet thing is about.
Not good enough. You should really be inspecting your CPU with a microscope.
It isn’t more dangerous than running a binary downloaded from them by any other means. It isn’t more dangerous than downloaded installer programs common with Windows.
TBH macOS has had the more secure idea of by default using sandboxes applications downloaded directly without any sort of installer. Linux is starting to head in that direction now with things like Flatpak.
What's stopping the downloaded script from wiping my home directory?
What's stopping any Makefile, build script, or executable from running rm -rf ~? The correct answer is "nothing". PPAs are similarly open, things are a little safer if you only use your distro's default package sources, but it's always possible that a program will want to be able to delete something in your home directory, so it always has permission.
Containerized apps are the only way around this, where they get their own home directory.
Don't forget your package manager, running someone's installer as root
It's roughly the same state as when windows vista rolled out UAC in 2007 and everything still required admin rights because that's just how everything worked....but unlike Microsoft, Linux distros never did the thing of splitting off installs into admin vs unprivileged user installers.
plenty of package managers have.
flatpak doesn't require any admin to install a new app
nixos doesn't run any code at all on your machine for just adding a package assuming it's already been cached. if it hasn't been cached it's run in a sandbox. the cases other package managers use post install configuration scripts for are a different mechanism which possibly has root access depending on what it is.
Gonna ignore nix since they have two users, but flatpak is fair. However flatpak is a sandboxing scheme which is distinct from per-user installs. In many cases it can be the better route but not always. I think the reason it's popular on Linux is also the dll hell problem.
idk if 2 users is fair, it may just be my circles but I see nixos mentioned more than almost anything else on lemmy/hn/etc in the past couple years
If you're worried, download it into a file first and read it.
This is just normal Linux poor security. Even giants like docker do this.
Docker doesn't do this anymore. Their install script got moved to "only do this for testing".
Use a convenience script. Only recommended for testing and development environments.
Now, their install page recommends packages/repos first, and then a manual install of the binaries second.
And don't forget to sudo!
The security concerns are often overblown. The bigger problem for me is I don't know what kind of mess it's going to make or whether I can undo it. If it's a .deb or even a tarball to extract in /usr/local then I know how to uninstall.
I will still use them sometimes but for things I know and understand - e.g. rustup will put things in ~/.rustup and update the PATH in my shell profile and because I know that's what it does I'm happy to use the automation on a new system.
Back up your data folks. You're probably more likely to accidentally rm -rf yourself than download a script that will do it.
To be fair that's because Linux funnels you to the safeguard-free terminal where it's much harder to visualize what's going on and fewer checks to make sure you're doing what you mean to be doing. I know it's been a trend for a long time where software devs think they are immune from mistakes but...they aren't. And nor is anyone else.