2 ms·
I can trust packages, since they're signed by a developer, or by a distribution. I can't trust that the content of a script I obtained via curl is from the deve
by falcolas 7y ago
I can trust packages, since they're signed by a developer, or by a distribution. I can't trust that the content of a script I obtained via curl is from the developer.
- dmitriid 7y agonpm has had multiple incidents with malicious packages [1][2]. apt had its own CVE [3] [1] https://securityaffairs.co/wordpress/88433/hacking/npm-installer-purescript-compromised.html https://securityaffairs.co/wordpress/88433/hacking/npm-insta... [2] https://securityaffairs.co/wordpress/74497/hacking/malicious-eslint-packages.html https://securityaffairs.co/wordpress/74497/hacking/malicious... [3] https://lists.debian.org/debian-security-announce/2019/msg00010.html https://lists.debian.org/debian-security-announce/2019/msg00...
- falcolas 7y agoNPM packages are not, to the best of my knowledge, cryptographically signed. If you're using them blindly, then you are indeed in the same camp as those who curl|sh. Needless to say, you shouldn't blindly install and run NPM scripts either. And if it takes a CVE to allow a MITM attack to inject a malicious payload into an apt package, that's already better than curl, which does not. It's also worth noting that the CVE had a stable fix available as of that announcement.
- dmitriid 7y ago> It's also worth noting that the CVE had a stable fix available as of that announcement. It's also worth noting that the problem was there before it was discovered, fixed, and then disclosed. Ultimately, it comes down to how paranoid you are about your sources of software: https://wiki.c2.com/?TheKenThompsonHack https://wiki.c2.com/?TheKenThompsonHack