Re: Reproducing distributed binaries

[phobos@xxxxxxxxxx]

A follow-up to this, since I noticed your mailer implies an Apple OS,
you could also get the source, inspect it, and follow the instructions
for "make dist-osx" to create your own mpkg which can be installed via
the Apple packaging system.  The "make dist-osx" setup is fairly trivial
to complete.  If you're skilled enough to read and understand the
source, and what it's actually doing, then chances are compiling the
code isn't that much of a mental stretch.

On Wed, Aug 17, 2005 at 09:46:36PM -0500, packwidth@xxxxxxxxx wrote 4.7K bytes in 88 lines about:
:  I know that this topic has been discussed quite exhaustively with  
: regard to other security applications, but here it goes again:
: 
:  What is necessary to determine that the binaries that are  
: distributed are actually compiled from the source tarball (same  
: checksum)?
: [This is assuming, of course, that one checks out the source and the  
: install scripts included with the binaries.]
:  I assume you'd need to use the same compiler, compiler version, and  
: compile options.  Anything else?
: 
:  I anticipate several responses suggesting that I just use the  
: binary that I compiled in order to test the distributed version!  But  
: there are advantages to using the prepackaged version (ie ease of  
: installation and distribution across several systems).  It would be  
: trivial to write a script to grab the tarball and the binary package,  
: uncompress and compile the source (according to compile specs  
: provided in the tarball?) then compare the two.  The script would  
: also output the diffed source (and install scripts) (from the  
: previous version) to let you examine the changes in the source code.
: 
:  If there were several people running a script like this with every  
: release, it would be considerably easier to detect the presence of a  
: trojaned binary package.
: 
: Any thoughts on the matter?
: 
: Cheers,
: Phil



--