On 03/08/2014 12:46 PM, Kern Sibbald wrote:
If you look carefully at my proposal, you will see that it facilitates
knowing where to make checksums without any compiler changes, which
means that it will work with any compiler and can be applied to the
binaries.
Finding out what *exactly* went into a binary is a complex problem. No
solution I have seen in the last 10 years gives perfect results and
depend on the build system behaving properly. I can tell you that this
is very often *not* the case. In consumer electronics binaries are
copied around after being built (and without source code so you cannot
verify). Libraries built with one system are used as binary components
in other build systems where the constraints of the first build system
might not apply (at the same time causing some pretty funky side effects
with the dynamic linker because dependencies no longer necessarily
match). Checksumming will only give you partial results and not 100%
accuracy that people on this list are talking about. This is why other
methods are, in my opinion, much more useful.
But, if you really want to work on it I suggest looking at Nix (
http://www.nixos.org/ ) first, since it already does a ton of
checksumming and where even small changes in the build environment are
taken into account. Good luck.
armijn
--
------------------------------------------------------------------------
[email protected] || http://www.gpl-violations.org/
------------------------------------------------------------------------
