libtar: more lenient tar checksum verification

Until now, the tar checksum verification simply copied the header,
recomputed the checksum and compared it byte-for-byte with the
original.

However, not all implementations store the checksum the same way. For
instance, git-archive generates tar balls that use the same format as
for other octal numbers.

This patch makes the checksum verification more lenient by parsing the
checksum from the header and comparing it with the computed value
instead of copying the entire block and insisting on byte-for-byte
equivalence.

The result is better interoperabillity with existing tools and perhaps
slightly faster processing since the block doesn't have to be copied.

Reported-by: Matt Turner <mattst88@gmail.com>
Suggested-by: René Scharfe <l.s.r@web.de>
Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>

0 files changed, 0 insertions, 0 deletions