30 | | The goal of ''this'' ticket is to have documentation of the ways in which Tahoe-LAFS builds are not currently verifiable. Its scope includes only Tahoe-LAFS as built via setup.py (using setuptools and/or pip), not as packaged by an operating system distribution or package management system. However, it may be useful to consider how existing projects have approached this problem: [https://wiki.debian.org/ReproducibleBuilds Debian], [https://blog.torproject.org/category/tags/deterministic-builds Tor], [https://en.bitcoin.it/wiki/Release_process Bitcoin], and the recent ad-hoc [https://madiba.encs.concordia.ca/~x_decarn/truecrypt-binaries-analysis/ reproduction of the TrueCrypt Windows binaries]. |
| 30 | The goal of ''this'' ticket is to have documentation of the ways in which Tahoe-LAFS builds are not currently verifiable. Its scope includes: |
| 31 | |
| 32 | * Tahoe-LAFS as built via setup.py (using setuptools and/or pip), and |
| 33 | * the MAC OS X (#182) and Windows (#195) packages |
| 34 | |
| 35 | but does not include Tahoe-LAFS as packaged by an operating system distribution or package management system. |
| 36 | |
| 37 | It may be useful to consider how existing projects have approached this problem: [https://wiki.debian.org/ReproducibleBuilds Debian], [https://blog.torproject.org/category/tags/deterministic-builds Tor], [https://en.bitcoin.it/wiki/Release_process Bitcoin], and the recent ad-hoc [https://madiba.encs.concordia.ca/~x_decarn/truecrypt-binaries-analysis/ reproduction of the TrueCrypt Windows binaries]. |