Difference between revisions of "Reproducible builds"
| Line 12: | Line 12: | ||
== Speakers == | == Speakers == | ||
Reproducible Builds: [http://layer-acht.org/ Holger Levsen] | Reproducible Builds: [http://layer-acht.org/ Holger Levsen] | ||
| + | |||
Tor Q&A: Lunar [https://blog.torproject.org/blogs/lunar Lunar] | Tor Q&A: Lunar [https://blog.torproject.org/blogs/lunar Lunar] | ||
Latest revision as of 01:15, 4 December 2015
 |
Starts | Organizer |
|---|---|---|
| Fri 04 Dec 2015 18:00 | Everyoooooneee!!!!!!!111 | |
| Ends | Event Owner | |
| Fri 04 Dec 2015 21:00 | User:Kargig |
Reproducible Builds rooock!
Speakers
Reproducible Builds: Holger Levsen
Tor Q&A: Lunar Lunar
What is it about?
Reproducible builds are a set of software development practices which create a verifiable path from human readable source code to the binary code used by computers.
Why does it matter?
Most aspects of software verification are done on source code, as that is what humans can reasonably understand. But most of the time, computers require software to be first built into a long string of numbers to be used. With reproducible builds, multiple parties can redo this process independently and ensure they all get exactly the same result. We can thus gain confidence that a distributed binary code is indeed coming from a given source code.
What made the recent Volkswagen emissions scandal possible is software that has been designed to lie about its sensors in a lab environment. Having the source code under public scrutiny would have made adding such a misfeature only a little more difficult. Without reproducible builds, it is hard to confirm that the binary code installed in the car was actually made using the source code that has been verified.
Several free software projects already, or will soon, provide reproducible builds.
More
Learn more about reproducible builds at reproducible builds website
