Bug 719139 - Zlib fails to read zip64 files on 64-bit system
Summary: Zlib fails to read zip64 files on 64-bit system
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: zlib
Version: 14
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peter Schiffer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-05 20:52 UTC by Brian Sipos
Modified: 2012-01-25 22:34 UTC (History)
1 user (show)

Fixed In Version: zlib-1.2.5-6.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-17 20:28:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Minimal test source (1.55 KB, text/x-csrc)
2011-07-05 20:52 UTC, Brian Sipos
no flags Details
Minimal test running environment (280 bytes, application/x-shellscript)
2011-07-05 20:53 UTC, Brian Sipos
no flags Details
Example patch which resolves bug (3.83 KB, patch)
2011-07-05 21:01 UTC, Brian Sipos
no flags Details | Diff

Description Brian Sipos 2011-07-05 20:52:41 UTC
Created attachment 511388 [details]
Minimal test source

Description of problem:
The zlib extension minizip (package minizip and minizip-devel) does not properly identify size overflow conditions in zip64 files when the host system is actually 64-bit native.

Version-Release number of selected component (if applicable):
1.2.5-2.fc14

How reproducible:
Consistently

Steps to Reproduce:
1. Install package minizip-devel
2. Run attached run_test.sh script to create large zip file and attempt to read.
3. Observe three failures.
  
Actual results:
The minimal test program fails to detect large file size correctly, and fails when opening files beyond 4GiB point in Zip archive file.
Failure output "Contains 'large.test', size 0xFFFFFFFF bytes".
Failure output "opening file failed: -103"
Failure output "closing file failed: -102"

Expected results:
Expect output "Contains 'large.test', size 0x119400000 bytes".
Expect output "opening file succeeded"
Expect output "closing file succeeded"


Additional info:
See attached test program for detailed failure info and attached patch for a possible fix.

Comment 1 Brian Sipos 2011-07-05 20:53:27 UTC
Created attachment 511389 [details]
Minimal test running environment

Comment 2 Brian Sipos 2011-07-05 21:01:54 UTC
Created attachment 511391 [details]
Example patch which resolves bug

This patch is against the zlib source package, which is used to build minizip and minizip-devel.

Comment 3 Fedora Admin XMLRPC Client 2011-07-12 11:52:20 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Peter Schiffer 2012-01-11 12:39:39 UTC
fixed in:
zlib-1.2.5-6.fc17
http://koji.fedoraproject.org/koji/buildinfo?buildID=282629

Comment 5 Fedora Update System 2012-01-11 14:04:02 UTC
zlib-1.2.5-6.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/zlib-1.2.5-6.fc16

Comment 6 Fedora Update System 2012-01-11 20:53:27 UTC
Package zlib-1.2.5-6.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing zlib-1.2.5-6.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-0385/zlib-1.2.5-6.fc16
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2012-01-16 12:53:47 UTC
zlib-1.2.5-6.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/zlib-1.2.5-6.fc15

Comment 8 Fedora Update System 2012-01-17 20:28:26 UTC
zlib-1.2.5-6.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2012-01-25 22:34:08 UTC
zlib-1.2.5-6.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.