On Fri, 2002-01-04 at 12:04, Sean Neakums wrote:
> begin Austin Gonyou quotation:
>
> > No, It does not guarantee. Also, if you're not on the same Inode the
> > file time is different, etc, it's possible to have different md5sums. A
> > basic size and file comparison is probably best for what you want to do.
>
> The md5sum of a file is based on its contents only. The inode has
> nothing to do with it.
>
> > Something you can do to test what I'm talking about is copy each of your
> > dumps to another name, binfilexyz.1 or something, then compare it's
> > md5sum against the original. Those should be the only time they match.
>
> I'm not sure exaclty what you mean by this. The name of the file is
> irrelevant in the computation of the md5sum.
A lot of binaries have generated strings put into them which are
created, an example would be:
cpp -E << /EOF
__TIME__
/EOF
# 1 ""
"12:25:35"
Compilers can also put strings into .o files which include the time
stamp and absolute pathnames.
Steve
>
> --
> ///////////////// | | The spark of a pin
> <sneakums@xxxxxxxx> | (require 'gnu) | dropping, falling feather-like.
> \\\\\\\\\\\\\\\\\ | | There is too much noise.
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@xxxxxxx
|