no support for ././@LongLink for long filenames in phar tar support

Bug #49910

Submitted:

2009-10-18 04:27 UTC

Modified:

2018-02-04 16:39 UTC

Votes:	6
Avg. Score:	4.8 ± 0.4
Reproduced:	4 of 4 (100.0%)
Same Version:	4 (100.0%)
Same OS:	3 (75.0%)

From:

cellog@php.net

Assigned:

bishop (profile)

Status:

Closed

Package:

PHAR related

PHP Version:

5.3SVN-2009-10-18 (SVN)

OS:

n/a

Private report:

CVE-ID:

None

[2009-10-18 04:27 UTC] cellog@php.net

Description:
------------
The arcane (and poorly documented) ././@LongLink method of storing long filenames is not supported by ext/phar.

The header stores the size of the filename, and the next block stores the filename itself.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports

[2009-11-12 03:53 UTC] cellog@php.net

read support enabled.  Will keep this open while I decide whether to also implement write support for filenames > 256 characters

[2017-10-24 05:27 UTC] kalle@php.net

-Status: Assigned +Status: Open -Assigned To: cellog +Assigned To:

[2018-02-04 16:39 UTC] bishop@php.net

-Status: Open +Status: Closed -Assigned To: +Assigned To: bishop

[2018-02-04 16:39 UTC] bishop@php.net

Based on subsequent commits (including a test), a quick read of the code, and a description of the GNU tar[1] support, I believe this bug has been fixed. Please feel free to re-open if there is still work left to do.

[1]: https://stackoverflow.com/q/2078778/2908724