hashpipe

You could use hashpipe (https://github.com/jbenet/hashpipe), from Juan Benet (the author of IPFS). It simply checks that the input to the command matches a given hash, so you can do `curl <url> | hashpipe <hash> | sh`, and if the output of the curl command is different than expected it won't be passed in to `sh`.

One of the biggest complaints about the curl - bash paradigm are the security implications. URLs can point to different content at different times. Project maintainers can (and have) changed the content at these URLs for malicious or other reasons. A lot of people will not examine the source of what they're piping into the shell. To me, https://github.com/jbenet/hashpipe addresses a lot of these issues by pinning the content to a hash. You can't force somebody to read and understand the install script, but at least those who do can know it's the one they verified in advance.

Recently I stumbled across hashpipe: "hashpipe helps you venture into the unknown. It reads from stdin, checks the hash of the content, and outputs it IF AND ONLY IF it matches the provided hash checksum." [https://github.com/jbenet/hashpipe]

> Would this be better if the pasted command included some checksum which was checked before piping into the `sh`? hashpipe does exactly that: https://github.com/jbenet/hashpipe

All great ideas! mind adding some to https://github.com/jbenet/hashpipe/issues ? over time we can implement some

great point. if you have a good idea of how hashpipe should do it better pls comment at: https://github.com/jbenet/hashpipe/issues at least hashpipe stops the output, so this would not run the bad code. hashpipe would stop it: cat evil | hashpipe <some-other-hash> | sh without pipefail, it would still exit 0, but at least the evil would be contained.

you're right https://github.com/jbenet/hashpipe/issues/3

yeah, hashes are decided by every single bit including the last one, and not a single bit should be output until the hash matches. It currently buffers everything in memory, but might do this: https://github.com/jbenet/hashpipe/issues/1 (some settings dont have disk though). hashpipe is intended for most executable use cases (usually under <50MB)