Joe Tsai a04b4ddba4 archive/tar: properly parse GNU base-256 encoding ... Motivation: * Previous implementation did not detect integer overflow when parsing a base-256 encoded field. * Previous implementation did not treat the integer as a two's complement value as specified by GNU. The relevant GNU specification says: <<< GNU format uses two's-complement base-256 notation to store values that do not fit into standard ustar range. >>> Fixes #12435 Change-Id: I4639bcffac8d12e1cb040b76bd05c9d7bc6c23a8 Reviewed-on: https://go-review.googlesource.com/17424 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>		2016-02-03 07:01:09 -05:00
..
gnu-multi-hdrs.tar	archive/tar: convert Reader.Next to be loop based	2016-02-03 06:58:30 -05:00
gnu.tar
hardlink.tar	archive/tar: fix round-trip attributes	2015-08-21 00:15:22 -04:00
hdr-only.tar	archive/tar: make output deterministic	2016-02-02 14:10:11 -05:00
issue10968.tar	archive/tar: terminate when reading malformed sparse files	2015-08-21 00:15:22 -04:00
issue11169.tar	archive/tar: add missing error checks	2015-08-21 00:15:22 -04:00
issue12435.tar	archive/tar: properly parse GNU base-256 encoding	2016-02-03 07:01:09 -05:00
neg-size.tar	archive/tar: make output deterministic	2016-02-02 14:10:11 -05:00
nil-uid.tar
pax-multi-hdrs.tar	archive/tar: convert Reader.Next to be loop based	2016-02-03 06:58:30 -05:00
pax-path-hdr.tar	archive/tar: move parse/format methods to standalone receiver	2016-02-02 14:32:27 -05:00
pax.tar
small.txt
small2.txt
sparse-formats.tar
star.tar
ustar-file-reg.tar	archive/tar: move parse/format methods to standalone receiver	2016-02-02 14:32:27 -05:00
ustar.tar
v7.tar
writer-big-long.tar
writer-big.tar
writer.tar
xattrs.tar