You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2010/03/12 16:13:27 UTC
[jira] Created: (COMPRESS-101) ZipArchiveINputStream doesn't handle
data descriptors with signatures
ZipArchiveINputStream doesn't handle data descriptors with signatures
---------------------------------------------------------------------
Key: COMPRESS-101
URL: https://issues.apache.org/jira/browse/COMPRESS-101
Project: Commons Compress
Issue Type: Bug
Affects Versions: 1.0
Reporter: Stefan Bodewig
Assignee: Stefan Bodewig
Fix For: 1.1
from http://www.pkware.com/documents/casestudies/APPNOTE.TXT :
{quote}
Although not originally assigned a signature, the value
0x08074b50 has commonly been adopted as a signature value
for the data descriptor record. Implementers should be
aware that ZIP files may be encountered with or without this
signature marking data descriptors and should account for
either case when reading ZIP files to ensure compatibility.
When writing ZIP files, it is recommended to include the
signature value marking the data descriptor record. When
the signature is used, the fields currently defined for
the data descriptor record will immediately follow the
signature.
{quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COMPRESS-101) ZipArchiveInputStream doesn't handle
data descriptors without signatures
Posted by "Stefan Bodewig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMPRESS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Bodewig updated COMPRESS-101:
------------------------------------
Description:
from http://www.pkware.com/documents/casestudies/APPNOTE.TXT :
{quote}
Although not originally assigned a signature, the value
0x08074b50 has commonly been adopted as a signature value
for the data descriptor record. Implementers should be
aware that ZIP files may be encountered with or without this
signature marking data descriptors and should account for
either case when reading ZIP files to ensure compatibility.
When writing ZIP files, it is recommended to include the
signature value marking the data descriptor record. When
the signature is used, the fields currently defined for
the data descriptor record will immediately follow the
signature.
{quote}
The current code skips over 16 bytes while the descriptor may be using only 12 bytes.
was:
from http://www.pkware.com/documents/casestudies/APPNOTE.TXT :
{quote}
Although not originally assigned a signature, the value
0x08074b50 has commonly been adopted as a signature value
for the data descriptor record. Implementers should be
aware that ZIP files may be encountered with or without this
signature marking data descriptors and should account for
either case when reading ZIP files to ensure compatibility.
When writing ZIP files, it is recommended to include the
signature value marking the data descriptor record. When
the signature is used, the fields currently defined for
the data descriptor record will immediately follow the
signature.
{quote}
Summary: ZipArchiveInputStream doesn't handle data descriptors without signatures (was: ZipArchiveInputStream doesn't handle data descriptors with signatures)
> ZipArchiveInputStream doesn't handle data descriptors without signatures
> ------------------------------------------------------------------------
>
> Key: COMPRESS-101
> URL: https://issues.apache.org/jira/browse/COMPRESS-101
> Project: Commons Compress
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Stefan Bodewig
> Assignee: Stefan Bodewig
> Fix For: 1.1
>
>
> from http://www.pkware.com/documents/casestudies/APPNOTE.TXT :
> {quote}
> Although not originally assigned a signature, the value
> 0x08074b50 has commonly been adopted as a signature value
> for the data descriptor record. Implementers should be
> aware that ZIP files may be encountered with or without this
> signature marking data descriptors and should account for
> either case when reading ZIP files to ensure compatibility.
> When writing ZIP files, it is recommended to include the
> signature value marking the data descriptor record. When
> the signature is used, the fields currently defined for
> the data descriptor record will immediately follow the
> signature.
> {quote}
> The current code skips over 16 bytes while the descriptor may be using only 12 bytes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COMPRESS-101) ZipArchiveInputStream doesn't handle
data descriptors with signatures
Posted by "Stefan Bodewig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMPRESS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Bodewig updated COMPRESS-101:
------------------------------------
Summary: ZipArchiveInputStream doesn't handle data descriptors with signatures (was: ZipArchiveINputStream doesn't handle data descriptors with signatures)
> ZipArchiveInputStream doesn't handle data descriptors with signatures
> ---------------------------------------------------------------------
>
> Key: COMPRESS-101
> URL: https://issues.apache.org/jira/browse/COMPRESS-101
> Project: Commons Compress
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Stefan Bodewig
> Assignee: Stefan Bodewig
> Fix For: 1.1
>
>
> from http://www.pkware.com/documents/casestudies/APPNOTE.TXT :
> {quote}
> Although not originally assigned a signature, the value
> 0x08074b50 has commonly been adopted as a signature value
> for the data descriptor record. Implementers should be
> aware that ZIP files may be encountered with or without this
> signature marking data descriptors and should account for
> either case when reading ZIP files to ensure compatibility.
> When writing ZIP files, it is recommended to include the
> signature value marking the data descriptor record. When
> the signature is used, the fields currently defined for
> the data descriptor record will immediately follow the
> signature.
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (COMPRESS-101) ZipArchiveInputStream doesn't
handle data descriptors without signatures
Posted by "Stefan Bodewig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMPRESS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Bodewig resolved COMPRESS-101.
-------------------------------------
Resolution: Fixed
svn revision 922298 but untested since I've failed to create such an archive so far.
> ZipArchiveInputStream doesn't handle data descriptors without signatures
> ------------------------------------------------------------------------
>
> Key: COMPRESS-101
> URL: https://issues.apache.org/jira/browse/COMPRESS-101
> Project: Commons Compress
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Stefan Bodewig
> Assignee: Stefan Bodewig
> Fix For: 1.1
>
>
> from http://www.pkware.com/documents/casestudies/APPNOTE.TXT :
> {quote}
> Although not originally assigned a signature, the value
> 0x08074b50 has commonly been adopted as a signature value
> for the data descriptor record. Implementers should be
> aware that ZIP files may be encountered with or without this
> signature marking data descriptors and should account for
> either case when reading ZIP files to ensure compatibility.
> When writing ZIP files, it is recommended to include the
> signature value marking the data descriptor record. When
> the signature is used, the fields currently defined for
> the data descriptor record will immediately follow the
> signature.
> {quote}
> The current code skips over 16 bytes while the descriptor may be using only 12 bytes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.