News for hackers. Stuff that matters.
Re:Unix Wildcards Gone Wild (2014) by craftyguy on Friday June 22, 2018 @10:43PM (#17379212)
or my personal favorite are folks who recommend this crap:

    curl https://<whatever> | bash
Re:Unix Wildcards Gone Wild (2014) by Spivak on Saturday June 23, 2018 @01:32AM (#17379698)
This really isn't as bad and people make it seem. If you're trusting the vendor and aren't going to read the code anyway it's no less safe than installing a package.

I don't like installations like this because they're messy, hard to track, harder to clean up, don't lend themselves to mass deployments, don't provide any integrity verification, the list goes on, but they're not particularly unsafe.

These things exist because there aren't good package that don't require root. Maybe we'll get there eventually.

Re:Unix Wildcards Gone Wild (2014) by jwilk on Saturday June 23, 2018 @06:20AM (#17380495)
One nasty thing about piping to shell is that the server can detect that this is happening:

https://news.ycombinator.com/item?id=11532599

Re:Unix Wildcards Gone Wild (2014) by craftyguy on Saturday June 23, 2018 @01:40AM (#17379725)
> If you're trusting the vendor

Yea, because urls and websites never change! And http can never be compromised! (nope)

> but they're not particularly unsafe.

Arbitrary execution is never safe!

> These things exist because there aren't good package that don't require root. Maybe we'll get there eventually.

Well, depending on the language, there are (e.g. pip crap). But maybe folks should produce packages that maintainers can, well, maintain.