Trust, Tampering, and Transparency: What History Can Teach Us About Open Source...
summary
Shows that a 1697 sealed letter is read non-destructively by MIT with x‑ray imaging and computational unfolding, and about 600 Hague letters remain sealed for analysis; frames letter locking as integrity baked into the artifact and chained libraries as physical access control analogous to npm/PyPI policies. Links early polyalphabetic ciphers (Alberti) to modern signing, reproducible builds, Sigstore, SLSA, in‑toto, Tekton, SBOMs and GUAC, noting open publication of code and practical tamper evidence.
AI-written summary · about
chapters (9)
- 0:00Open source security history
- 1:07Letter locking project
- 2:54Visari corridor
- 5:44Chained libraries
- 8:38Letter locking integrity
- 11:30Alberti’s cipher disc
- 14:40Renaissance ciphers to tools
- 16:28Openness drives security
- 17:31Question and answer session
related talks
05mThe Long Arc of Digital Rights: Securing our Open Source Future
30mSecuring Open Source Supply Chains
11mKeynote: Securing Open Source
40mSecurity: Why It _has_to Be Open Source
47mBuilding Trust in Open Source: A Practical Guide to Securing Your ...
17mKeynote: Fighting The Next War - Future Threats to OSS and Software Supply Chain...
22mBreaking the Sharing Paradox: A Working Foundation and a Call for…
30mSecuring the Open Source Software Supply Chain