| |||||||||||||
|
| |||||||||||||
Universal signing of source code and source packagesUniversal signing of source code and source packagesPosted Sep 15, 2008 12:33 UTC (Mon) by AndyBurns (subscriber, #27521)In reply to: Universal signing of source code and source packages by epa Parent article: Adding a signing key to RPM
I doubt building the same package, on the same machine twice would generate the exact same binary (timestamps would be included from __TIME__ macros) let alone building by different compilers/linkers, with different libraries installed.
(Log in to post comments)
Universal signing of source code and source packages Posted Sep 15, 2008 16:55 UTC (Mon) by jreiser (subscriber, #11027) [Link] building the same package ... different compilers/linkers ... libraries In the late 1980's Apollo Computer had DSEE (Domain Software Engineering Environment) which tracked not only source code but also tools and build scripts. DSEE did guarantee bit-identical outputs because it tracked and could re-generate everything that affected a build. An executable file had exactly one timestamp, in a designated field of the header. (There was no __TIME__.)
|
|
||||||||||||