This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients Kristof.Keppens, Paul, alanmcintyre, amaury.forgeotdarc, christian.heimes, craigds, dandrzejewski, enlavin, eric.araujo, lambacck, nadeem.vawda, segfault42, serhiy.storchaka
Date 2012-09-22.17:56:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <201209222056.07175.storchaka@gmail.com>
In-reply-to <1347975870.76.0.932550727049.issue9720@psf.upfronthosting.co.za>
Content
No, on the contrary, it is not such easy to fix, and the patch is incorrect. 
Sorry that it is not clear either. The size of the header with extra args 
depends on the size of the file. The file size can be changed in the process of 
compressing, and compressed size may be larger than uncompressed size, 
exceeding 32-bit boundary. Rewriting the header with extra args, we can 
overwrite compressed data.

I was put off the issue for further more careful research. Thanks for the 
reminder.

One solution is always (even for smallest files) to write 64-bit sizes when 
allowZip64 is true.
History
Date User Action Args
2012-09-22 17:56:23serhiy.storchakasetrecipients: + serhiy.storchaka, amaury.forgeotdarc, alanmcintyre, christian.heimes, nadeem.vawda, eric.araujo, lambacck, dandrzejewski, segfault42, craigds, enlavin, Paul, Kristof.Keppens
2012-09-22 17:56:23serhiy.storchakalinkissue9720 messages
2012-09-22 17:56:22serhiy.storchakacreate