CODEWITHSUNDEEP
linuxhashcompressionmd5tar
user3721976
user3721976

Reputation:

Why do the md5 hashes of two tarballs of the same file differ?

I can run:

echo "asdf" > testfile
tar czf a.tar.gz testfile
tar czf b.tar.gz testfile
md5sum *.tar.gz

and it turns out that a.tar.gz and b.tar.gz have different md5 hashes. It's true that they're different, which diff -u a.tar.gz b.tar.gz confirms.

What additional flags do I need to pass in to tar so that its output is consistent over time with the same input?

Upvotes: 23

Views: 8922

Answers (2)

JerryCauser
JerryCauser

Reputation: 885

For MacOS:

In man tar we can look at --options section and there we will find !timestamp option, which will exclude timestamp from our gzip archive. Usage:

tar --options '!timestamp' -cvzf archive.tgz filename

It will produce same md5 sum for same files with same names

Upvotes: 3

Barmar
Barmar

Reputation: 780974

tar czf outfile infiles is equivalent to

tar cf - infiles | gzip > outfile

The reason the files are different is because gzip puts its input filename and modification time into the compressed file. When the input is a pipe, it uses an empty string as the filename and the current time as the modification time.

But it also has a --no-name option, which tells it not to put the name and timestamp into the file. So if you write the expanded command explicitly, instead of using the -z option to tar, you can make use of this option.

tar cf - testfile | gzip --no-name > a.tar.gz
tar cf - testfile | gzip --no-name > b.tar.gz

I tested this on OS X 10.6.8 and it works.

Upvotes: 32

Related Questions