Description
Some tar files have UID and GID fields that start with the binary marker 0x80. The TarArchiveEntry is unable to cope with that since it assumes that UID and GID are always ASCII.
Attachments
Attachments
Issue Links
- is duplicated by
-
COMPRESS-177 TarArchiveInputStream rejects valid TAR file
- Resolved
- is part of
-
COMPRESS-182 Support big or even negative numbers in all numeric TAR headers
- Resolved