[ntp:hackers] MD5 checksums

Hal Murray hmurray at megapathdsl.net
Fri Jan 29 10:47:46 UTC 2010


Recently, webmaster at ntp.org said:
> MD5 sum:
> http://archive.ntp.org/ntp4/ntp-dev/ntp-dev-4.2.7p11.tar.gz.md5
> ftp://archive.ntp.org/ntp4/ntp-dev/ntp-dev-4.2.7p11.tar.gz.md5 

After I pull over the bits, I see:

$ md5sum -c ntp-dev-4.2.7p11.tar.gz.md5
md5sum: ntp-dev-4.2.7p11.tar.gz.md5: no properly formatted MD5 checksum lines 
found

$ md5sum ntp-dev-4.2.7p11.tar.gz
6616c76867970244c8a42ffe35142a91  ntp-dev-4.2.7p11.tar.gz

$ more ntp-dev-4.2.7p11.tar.gz.md5
sig1: md5      : 6616c76867970244c8a42ffe35142a91

My (linux/gnu) man page for md5sum says:
       -c, --check
              read MD5 sums from the FILEs and check them

       The sums are computed as described in RFC 1321.  When  checking,
       the  input  should  be  a  former  output  of this program.  The
       default mode is to print a line with checksum, a character indi-
       cating  type  (‘*’  for binary, ‘ ’ for text), and name for 
each
       FILE.


So how are the tar files made?  How are the md5 files made?

I'm running on a Linux system.  I'd like a script that would pull over the 
tar file and checksum, and then check the pair so I don't waste time chasing 
an obscure quirk/bug when it was really just an error at the TCP level.




-- 
These are my opinions, not necessarily my employer's.  I hate spam.





More information about the hackers mailing list