.buildinfo
server
In order to build packages reproducibly, you not only need identical
sources but also some external definition of the environment used for a
particular build. This definition includes the inputs and the outputs
and—in the Debian case—are available in a
$package_$architecture_$version.buildinfo
file.
It is not currently clear how these files could or should be handled in practice, hence the creation of this server to investigate.
0xB586FBCA67A0DDF7
0x9538881E43D098FB
jtx1b (Automatically generated key for signing .buildinfo files)
0xFD20BBE472905784
0xCDD42D70685A0E01
0x28F5F5D5FEE63ABA
0x4F15D07E60F07CB2
0xA6B59AB7CD69D4AC
profitbricks-build2-i386 (Automatically generated key for signing .buildinfo files)
0x1310D22166A88B5F
profitbricks-build6-i386 (Automatically generated key for signing .buildinfo files)
0xBFF95736F711C117
profitbricks-build15-amd64 (Automatically generated key for signing .buildinfo files)
0xBB1FD085171F6E18
profitbricks-build11-amd64 (Automatically generated key for signing .buildinfo files)
0x28F5F5D5FEE63ABA
0x2EB7D8A099C83DD8
0xAEC7FC78A3E8B530
0x2738E803AC4FE478
0x2EB7D8A099C83DD8
0xAEC7FC78A3E8B530
0xFAC0B94FFF2617A2
cbxi4b (Automatically generated key for signing .buildinfo files)
0xCDD42D70685A0E01
0x2EB7D8A099C83DD8
0x28F5F5D5FEE63ABA
$ gpg --output=- --clearsign my.buildinfo | curl -X PUT --max-time 30 --data-binary @- https://buildinfo.debian.net/api/submit