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 andreas.schawo
Recipients andreas.schawo, arigo, georg.brandl, loewis, mark.dickinson
Date 2009-03-18.11:20:16
SpamBayes Score 2.2076785e-13
Marked as misclassified No
Message-id <1237375220.22.0.991590455845.issue4228@psf.upfronthosting.co.za>
In-reply-to
Content
As I understand actually the zipfile module possibly creates damaged zip
files after version 2.4 because of '\x00\x00\x00\x00' instead of
'\xff\xff\xff\xff' as header offset. But without any error.

I think the _struct.c should be cleaned in any case. Because we only get
errors in zipfile module when damaged zip files are created. An error
would be appriciated instead of a silenty damaged zip file.

But, why don't boundary check the header offset in zipfile module in a
short private  function and returning '\xff\xff\xff\xff' in case of
overflow? Maybe all longs should be boundary checked if this seems
necassery.
History
Date User Action Args
2009-03-18 11:20:20andreas.schawosetrecipients: + andreas.schawo, loewis, arigo, georg.brandl, mark.dickinson
2009-03-18 11:20:20andreas.schawosetmessageid: <1237375220.22.0.991590455845.issue4228@psf.upfronthosting.co.za>
2009-03-18 11:20:18andreas.schawolinkissue4228 messages
2009-03-18 11:20:17andreas.schawocreate