3 ms·
There are better strategies than blindly relying on third party reputation. A primary approach is package management with hash databases, to ensure you are rece
by contingencies 10y ago
There are better strategies than blindly relying on third party reputation. A primary approach is package management with hash databases, to ensure you are receiving the same code as others. Another is the use of multiple implementations whose results are compared, recently discussed @ https://news.ycombinator.com/item?id=12666923 https://news.ycombinator.com/item?id=12666923
- wang_li 10y agoYou're still relying on the source to not be underhanded and malicious. Getting the same, reproducible build as everyone else only means you've got a lot of company. It doesn't mean there isn't malicious code or intentional "bugs."
- contingencies 10y agoYou are right, though with hashing you've got effective post-release protection against a compromised source injecting malicious data at the very least, which these days is probably more likely than an outright malicious source for most major packages. So it's not without value. The second approach, more of an architectural workaround than a true solution, can still be used to insulate from major issues.
- seanp2k2 10y agoYou can do that with curl + bash too. RVM does this: https://rvm.io/rvm/security https://rvm.io/rvm/security