News for hackers. Stuff that matters.
Re:Detecting the use of “curl – bash” server side by Sean1708 on Wednesday April 20, 2016 @05:42AM (#11533221)
What amuses me is that the people who are vehemently against using a bash script are often the same people who will run

    $ ./configure
    $ make
without a second thought.
Re:Detecting the use of “curl – bash” server side by koolba on Wednesday April 20, 2016 @06:47AM (#11533449)
Don't forget the most important part:

    sudo make install
Re:Detecting the use of “curl – bash” server side by rmc on Wednesday April 20, 2016 @08:49AM (#11533953)
If you use checkinstall(1) it'll see what `sudo make install` would do, and create a local package that would do that (e.g. a deb on ubuntu). This package can then be installed in the usual manner, which gives you uninstallability, transactionality, and ensures you don't overwrite any other files installed via a package. This is much better than curl|bash.
Re:Detecting the use of “curl – bash” server side by Sean1708 on Wednesday April 20, 2016 @09:51AM (#11534348)
Correct me if I'm wrong but can't you also run arbitrary code while installing packages?

Either way I'm not saying `curl | bash` is good, I'm just trying to point out that people have a very knee jerk reaction to it and pay no mind to things which are similarly as dangerous.

Re:Detecting the use of “curl – bash” server side by rmc on Wednesday April 20, 2016 @11:56AM (#11535335)
Yes, it runs arbitrary code. But checkinstall avoids other downsides from curl|bash
Re:Detecting the use of “curl – bash” server side by pif on Wednesday April 20, 2016 @06:57AM (#11533488)
Yes, but not as root!
Re:Detecting the use of “curl – bash” server side by crdoconnor on Wednesday April 20, 2016 @07:05AM (#11533518)
Re:Detecting the use of “curl – bash” server side by the8472 on Wednesday April 20, 2016 @08:24AM (#11533827)
we can get better compartmentalization than that with things like user namespaces (firejail[1]) or spawning a temporary user id[2]

[1] https://l3net.wordpress.com/projects/firejail/ [2] https://github.com/teran-mckinney/raru

Re:Detecting the use of “curl – bash” server side by nerdponx on Wednesday April 20, 2016 @07:45AM (#11533653)
But that means they have to steal the laptop in the two minute window before it goes to sleep.

It's not like your user password is 1234, right?

Re:Detecting the use of “curl – bash” server side by Zeeem on Thursday April 21, 2016 @12:19AM (#11539672)
When I got my last computer, I just copied my home directory over. Funnily enough, my old login sessions worked.
Re:Detecting the use of “curl – bash” server side by merb on Wednesday April 20, 2016 @06:20AM (#11533346)
Actually 99% of the Time this will install it to /usr/local
Re:Detecting the use of “curl – bash” server side by fjarlq on Wednesday April 20, 2016 @06:32AM (#11533387)
I disagree. Many (probably most) makefiles conform to the GNU Coding Standards, which recommend declaring "all" to be the default make target. `make all` does not install; that's what `make install` is for.

https://www.gnu.org/prep/standards/html_node/Standard-Target...

Re:Detecting the use of “curl – bash” server side by coldtea on Wednesday April 20, 2016 @06:46AM (#11533446)
The idea of the original parent comment on Make is not about well conforming makefiles.

The idea is that if one doesn't trust a random curl-ed install file, they shouldn't trust a downloaded makefile either -- and for the same reasons, yet tons of people complaint about the first, but have been using the latter for decades without complain...

Re:Detecting the use of “curl – bash” server side by coldtea on Wednesday April 20, 2016 @06:43AM (#11533432)
The idea is that the Makefile (and maybe configure?) could just as well as a "curled" install script contain ANY command, even "sudo rm -rf /".

It's not about where it will install it if it works fine.