3 ms·
Please see the Reproducible Builds project, a vital contribution to answering this question. https://reproducible-builds.org/ https://reproducible-builds.org/
by dankohn1 11y ago
Please see the Reproducible Builds project, a vital contribution to answering this question.
https://reproducible-builds.org/ https://reproducible-builds.org/
- marcosdumay 11y agoReproducible builds do not cut it. If you have a known good binary signature, you'd also have a known good source signature and wouldn't have the problem. Or, to put it in better words, where do you get the certificate to check your build from? At extreme paranoia levels, you simply can never be sure you have the same software as everybody else, thus the only safe alternative is reviewing your copy yourself. (How do you know the computer is showing you the correct contents of your files? Didn't think that well enough yet.)
- dankohn1 11y agoDiverse Double Compiling is a proven solution to the On Trusting Trust problem [0]. So, if a package maintainer signs a package and posts that signature on an https page, I can have a high level of confidence that the software I compile and run on my machine is identical. Here is some advice from Schneier on running secure software against a state-level adversary [1][2]. However, even that is not immune from a black bag job [3]. [0] http://www.dwheeler.com/trusting-trust/ http://www.dwheeler.com/trusting-trust/ [1] https://www.schneier.com/blog/archives/2013/10/air_gaps.html https://www.schneier.com/blog/archives/2013/10/air_gaps.html [2] https://www.schneier.com/blog/archives/2014/04/tails.html https://www.schneier.com/blog/archives/2014/04/tails.html [3] https://en.wikipedia.org/wiki/Black_bag_operation https://en.wikipedia.org/wiki/Black_bag_operation