3 ms·
also this a 1000 times: "Dependency slurping systems like NPM, CPAN, go get, and so on continue to freak me out. They might potentially be more dangerous than
by DyslexicAtheist 8y ago
also this a 1000 times:
"Dependency slurping systems like NPM, CPAN, go get, and so on continue to freak me out. They might potentially be more dangerous than manual dependency management, despite the huge risks of that practice, precisely because they make it ‘easy’ to grow your project’s dependency graph — and hence the number of individuals and organizations that you implicitly trust. (And their trustworthiness can suddenly change for the worse.)"
- zzzcpan 8y agoImplicit trust is easy to solve by forbidding it. If someone doesn't want to maintain his project anymore, someone else could make a fork and try to promote it and try to gain trust again, but not take over that project. While this particular problem can be solved, in reality it doesn't matter, because trusting third parties with all the poor security they have is a much bigger security hole.
- ThePhysicist 8y agoI always pin dependencies to fixed versions in production software, which makes it less likely that my toolchain gets poisoned by a rogue version update. Also, for languages that allow it I bundle dependencies locally (in Python e.g. using Wheels) or run my own registry proxy, which makes poisoning by registry takeover also less likely. Personally I think there are bigger threats than malicious dependencies, especially if an adversary specifically targets me. My biggest concern is what happens when someone takes over our CI/CD setup, as that gives way more access to an adversary.