[jira] [Resolved] (COMPRESS-398) Uncorrect string terminal symbol in entry when creating Tar archive using TarArchiveOutputStream

["Stefan Bodewig (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/COMPRESS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig resolved COMPRESS-398.
-------------------------------------
    Resolution: Not A Bug

I've updated the documentation and created COMPRESS-419 as enhancement request for possible extensions.

> Uncorrect string terminal symbol in entry when creating Tar archive using TarArchiveOutputStream
> ------------------------------------------------------------------------------------------------
>
>                 Key: COMPRESS-398
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-398
>             Project: Commons Compress
>          Issue Type: Bug
>          Components: Archivers
>    Affects Versions: 1.14
>            Reporter: Yaroslav Trymbach
>            Priority: Minor
>
> I create Tar archive using TarArchiveOutputStream. And I've got one contradiction in output achive file with Tar-file format specification.
> https://www.gnu.org/software/tar/manual/html_node/Standard.html#SEC186 
> Specification has next sentention for entry header fields:
> "The name, linkname, magic, uname, and gname are null-terminated character strings. All other fields are zero-filled octal numbers in ASCII. Each numeric field of width w contains w minus 1 digits, and a null."
> But in file generated TarArchiveOutputStream octal numbers fields (mode, size, checksum etc) has terminated character not NULL (0x00) but SPACE (0x20), so some programs have problems while work with this files.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)