3 ms·
At the risk of replying to an overtly aggressive post on language bashing nonetheless - can you explain why rustups implementation of `curl https://sh.rustup.rs
by zamadatix 5y ago
At the risk of replying to an overtly aggressive post on language bashing nonetheless - can you explain why rustups implementation of `curl https://sh.rustup.rs https://sh.rustup.rs | sh` is worth mentioning? My understanding, from the 1,000 other times these flames start, is it's done properly and no more dangerous than any other way of running 3rd party binaries from a remote source.
Regardless of any other thoughts on Rust folks I'll tip my hat to them for they definitely have made talking about security more common... one way or another apparently :).
- busterarm 5y agohttps://news.ycombinator.com/item?id=6650987 https://news.ycombinator.com/item?id=6650987 https://blog.dijit.sh//don-t-pipe-curl-to-bash https://blog.dijit.sh//don-t-pipe-curl-to-bash https://sysdig.com/blog/friends-dont-let-friends-curl-bash/ https://sysdig.com/blog/friends-dont-let-friends-curl-bash/ https://www.seancassidy.me/dont-pipe-to-your-shell.html https://www.seancassidy.me/dont-pipe-to-your-shell.html
- steveklabnik 5y agoMany of the things in this link are avoided by our script. For example, that last one is made impossible by putting the contents of what is to be executed in a function, and then invoking that function at the end. If the connection closes early, nothing will be executed. The last ones are the same as any other way of downloading software that's executable, and not specific to curl | bash.