5 ms·
Download and look before running gives you an opportunity to spot something that's obviously, totally wrong... Not that one always uses that chance but at least
by h2odragon 7y ago
Download and look before running gives you an opportunity to spot something that's obviously, totally wrong... Not that one always uses that chance but at least you had it.
Installer systems that chain these "download and run" scripts (Node RED is the most recent I've used) scare me despite all the valid points TFA makes. "Not invented here / history must be reinvented" seems like philosophical point for some of these systems.
- actionowl 7y agoAlso, I know what git, configure, and make are supposed to do when invoked. I have no idea what piping a random script to sh is supposed to do without reading it.
- notacoward 7y agoYou might be surprised. As the OP mentions, configure scripts could contain literally anything. Ditto makefiles. If you're not reading them, you really have no idea what they might do. It's a little harder to embed something awful in git, but with hooks etc. it's not impossible. So when you do "git clone" and "configure" and "make" you're just as subject to vulnerabilities from file replacement or DNS hijacking, and there are just as many opportunities for something bad to happen as if you had piped curl through bash. This is why checking signatures is the most important part of code distribution. It doesn't solve every problem, but it solves most. At least then you know whose code you're getting, and that they attest to the code's validity (including safety). Maybe they're wrong or maybe they're not as good as you thought they were, but it's still a big improvement.
- actionowl 7y agoIf we ignore the potential security issues with either approach for a moment and assume for the sake of argument that neither is more risky than the other I "might be surprised" by the behavior of running `./configure` or `make install` but I will almost always be surprised by the behavior downloading and running a random shell script. I prefer a package over either case, but lacking a package I'd prefer to use something that has some expectations of how it should behave. As a packager I find that software with a Makefile, CMakeLists.txt, or a configure script is likely to be easier to package than something that just provides a shell script. Those might still need to be patched or tweaked but there's an expectation that it's going to try to behave a certain way.
- ComodoHacker 7y agoAlso gives the same opportunity to your AV software if you happen to have one.
- UI_at_80x24 7y agoI agree 100%, all this does is reinforce the errors of the past and trains end users to be dumb. This is NO DIFFERENT then Windows users double-clicking on every email attachment. Every time somebody suggests this, the author needs to get slapped with a trout. Copy/Pasting code to get entered is BAD ENOUGH; nobody learns anything that way AND it is not secure! In a race to the bottom everyone looses.
- t0astbread 7y agoThere is a difference between downloading, say, the Docker install script from docker.com and opening a random email attachment and that is that I trust docker.com. If I don't trust docker.com because I think it might deliver malware in the install script or a poorly written install script, then I shouldn't use Docker because why would anything different apply to their main software. If I don't trust docker.com because I fear it might be hijacked then I shouldn't use Docker because who guarantees me that their source code or any derived binaries aren't also hijacked.
- UI_at_80x24 7y agoThat trust comes from education and experience. Just like an experienced computer user could launch an email attachment safely if they know what they are doing. My point is telling new users to blindly copy/paste/autorun ALL scripts just to get $thing to work only hurts US (FOSS proponents) and the end user.