News for hackers. Stuff that matters.
Re:The Case of the Modified Binaries by yourad_io on Friday October 24, 2014 @08:13AM (#8503241)
Still better than seeing this as "installation instructions":

    curl http://not-ssl.somesite.ru/ba.sh | bash
Often without an https:// option available at all.
Re:The Case of the Modified Binaries by emillon on Friday October 24, 2014 @10:03AM (#8503670)
I've made a list here:

http://curlpipesh.tumblr.com/

Re:The Case of the Modified Binaries by yonran on Friday October 24, 2014 @12:07PM (#8504308)
The vast majority of your weblog postings describe https downloads, so it is mostly tangential to grandparent’s complaint and to the article. A .sh script may be a messier and less idiomatic file format than .pkg/.deb/.rpm/.msi, but a pkg from an unknown server is just as dangerous as a shell script from an unknown server.
Re:The Case of the Modified Binaries by zxcdw on Friday October 24, 2014 @11:30AM (#8504139)
Please add the case of Rust package manager Cargo, found at http://crates.io
Re:The Case of the Modified Binaries by emillon on Friday October 24, 2014 @11:47AM (#8504215)
Done. Thanks!
Re:The Case of the Modified Binaries by yourad_io on Friday October 24, 2014 @12:37PM (#8504495)
My personal beef is with curling HTTP (no -s) URLs - getting an installation shell script over HTTPS is not unreasonable (unless instructed to provide a no-SSL-confirmation flag, such as -k for curl, in which case it is more or less the same thing).

By default, `curl https://blah.blah/` will only work if the TLS certs are proper & validated. This isn't about trusting the author (you'll be running their code anyway, one way or another) but the transport medium (HTTP!s).

If I had your show-and-shame tumblr, I'd only include http:// links.