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.
Created on 2010年11月03日 14:00 by rep, last changed 2022年04月11日 14:57 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| zipfile_recover_commentsize.patch | rep, 2010年11月03日 14:00 | review | ||
| Messages (2) | |||
|---|---|---|---|
| msg120326 - (view) | Author: (rep) | Date: 2010年11月03日 14:00 | |
Opening (and thus extracting) zip files with appended junk data is not possible with the way the current zipfile implementation checks validity. Basically the problem comes down to the comment size in the end-of-central-directory record being different from the size of the data following that record. Unix unzip and similar utilities handle that case by looking at the eocd-record and taking that as the correct value. Zip files with data appended to them will be extracted just fine with these tools. In python's zipfile the _EndRecData function will return None if the comment size does not match the record's value. The patch modifies this behaviour and takes only the portion of trailing data that the record specifies and due to that it does not raise BadZipfile exceptions if there's any junk data appended to a zip file. |
|||
| msg128278 - (view) | Author: (rep) | Date: 2011年02月10日 10:27 | |
superseded by issue 10694 |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:57:08 | admin | set | github: 54507 |
| 2011年02月10日 10:27:14 | rep | set | status: pending -> closed messages: + msg128278 resolution: accepted |
| 2011年02月10日 10:26:34 | rep | set | status: languishing -> pending |
| 2011年02月10日 10:26:28 | rep | set | status: open -> languishing |
| 2010年11月04日 17:55:09 | eric.araujo | set | keywords:
+ needs review nosy: + alanmcintyre stage: patch review versions: + Python 3.1, Python 3.2 |
| 2010年11月03日 14:00:37 | rep | create | |