3 ms·
Your mistake is assuming that people only do that for curl|sh — in my experience, the same percentage (high) will manually download and run a program / shell sc
by acdha 7y ago
Your mistake is assuming that people only do that for curl|sh — in my experience, the same percentage (high) will manually download and run a program / shell script, add an APT/YUM repository, etc. Once someone decides they need to run something the details aren’t very significant.
The problem isn’t curl but the challenge of trusting code. The default needs to be either Apple-style sandboxing (note how you get prompted if a new program tries to access your pictures, contacts, etc.) or something like Docker where the default is private with exceptions for the resources you enable.
- falcolas 7y agoPackage managers at least provide a path to trust - the PGP web of trust. curl|sh does not provide any path to (cryptographically secured) trust.
- acdha 7y agoThat's only for people using the global trust mechanism in a mainstream repo. If you think about it from a security perspective, how much difference does installing some random project's GPG signing key make?