News for hackers. Stuff that matters.
Re:“Curl Bash piping” wall of shame by ams6110 on Friday October 21, 2016 @10:35PM (#12766766)
A downloaded installer can be signed, and you can verify signatures or at least checksums out-of-band.
Re:“Curl Bash piping” wall of shame by recursive on Friday October 21, 2016 @11:07PM (#12766897)
That just asserts that it's the same series of bytes that was originally provided. You still have to trust the provider.
Re:“Curl Bash piping” wall of shame by njharman on Friday October 21, 2016 @11:23PM (#12766955)
Right, we know that security is a gradient, do you?

There is a quantitative difference between covering your laptop under a coat and locking the car doors and leaving it on bench when you take a walk around park.

Just as there is difference between piping the internet to root shell and installing a signed package that has whole ecosystem and many users validating and looking at it.

Re:“Curl Bash piping” wall of shame by foota on Saturday October 22, 2016 @12:28AM (#12767185)
In fairness, ssl from a trusted host is pretty similar.
Re:“Curl Bash piping” wall of shame by falcolas on Saturday October 22, 2016 @10:38AM (#12768837)
You're trusting the provider of the program, not the provider of the server. Curl/bash from github? You're trusting Github to provide the correct content; there have been times before where people have been able to spoof other users. Signatures on the package (or the code) would prevent an issue like this.
Re:“Curl Bash piping” wall of shame by myhf on Saturday October 22, 2016 @01:23AM (#12767339)
You always have to trust the provider. If you don't authenticate the message you also have to trust every carrier.
Re:“Curl Bash piping” wall of shame by na85 on Saturday October 22, 2016 @12:11AM (#12767145)
At least you avoid javascript pastejacking in this manner.