[docs] [issue25255] Security of CPython Builds
report at bugs.python.org
Mon Sep 28 20:53:23 CEST 2015
phelix added the comment:
@Brett: Thanks for the info, I had not noticed PEP 101 had been updated.
@Paul: Ah, I had not found PCBuild/readme.txt yet. I did look at the devguide but I got the impression it was mostly meant for debug builds.
> Basically through trusting the people who produce the builds.
I assume these builders are very experienced and well known developers (thanks btw I like Python very much). I would trust them a very long way.
But it is not their integrity that is in question. Python is so popular that there might be large monetary (and other) incentives to force builders into something. Just for Bitcoin alone probably millions of dollars.
I was only recently made aware about this from Namecoin team members (and this  video about reproducible builds from CCC14) but as far as I see it now there is a very valid core in their argumentation.
Our well respected team member Joseph Bisch has looked into reproducible builds of CPython and concluded that it might a difficult thing to do with a project as large as Python . But maybe there are other ways to make builds more secure? I realize it is a lot I am asking here but build security will certainly get more and more important with time. Could things be improved by getting several developers together to create a secure VM as a starting point that make reproducible builds easier?
Python tracker <report at bugs.python.org>
More information about the docs