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
..
testdata	archive/tar: properly parse GNU base-256 encoding	2016-02-03 07:01:09 -05:00
common.go	archive/tar: make output deterministic	2016-02-02 14:10:11 -05:00
example_test.go	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00
reader.go	archive/tar: properly parse GNU base-256 encoding	2016-02-03 07:01:09 -05:00
reader_test.go	archive/tar: properly parse GNU base-256 encoding	2016-02-03 07:01:09 -05:00
stat_atim.go	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00
stat_atimespec.go	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00
stat_unix.go	archive/tar: don't treat multiple file system links as a tar hardlink	2015-08-21 00:15:22 -04:00
tar_test.go	archive/tar: move round-trip reading into common os file	2015-08-21 00:15:22 -04:00
writer.go	archive/tar: properly format GNU base-256 encoding	2016-02-03 06:58:30 -05:00
writer_test.go	archive/tar: properly format GNU base-256 encoding	2016-02-03 06:58:30 -05:00