Bad zip

It looks like that fixed it. Based on a stackover flow I saw I would guess the. Closing issue. Sorry, something went wrong. Skip to content. Star New issue. Jump to bottom. It's not multi-part - it's just one large zip file btw.

I do not have the original data - all I have is the zipped file which means I cannot try to zip the content again just so you know. This does not seem to affect every subfolder or file respectively in the archive but for a lot of them the process seems to fail.

I ran into the same problem - a huge zip file with a lot of files - and unzip choked trying to unpack it. A possible solution is to use java archiver. Just unpack your stuff with jar xvf file. I just wanted to copy the comment into an answer, although I had to use the "try harder" -FF option to get it to work:. Suggestion online and via man pages is to use: zip -F original. Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? See Trademarks for appropriate markings. View All Products. Services Consulting Education Modernization Outsourcing. Characters Remaining: Please provide feedback! Error "Bad zip file" opening entry in zip file. Printable View. Title Error "Bad zip file" opening entry in zip file.

Article Number Environment Moveit Automation. What I mean by that is that say a. The same. The password is dominique for both of the zips. Do note that each. Now if you do python Program. Same goes for zipv2 but Congrats. No trouble extracting the. But if you try the same thing with John The Ripper.

John The Ripper Jr. John The Ripper. John The Ripper v2. I am unsure why this is happening and cannot find an answer for this issue anywhere. Its totally unknown from what I can tell and I can't find a way to debug or solve this issue. Tried generating more. Same method; a larger and smaller version of the. So I believe it has to do with the lines after the password is at. So in this case Line ; where the script doesn't stop after Line ?

I am not sure why does this work though. It isn't a solution but a step towards the solution I guess Now if I use this both zips are extracted successfully, just like the previous instances. BUT this time zipv1. But the same thing cannot be said regarding zipv2. The scenario is complex quite far away from an M CVE , I'd say , there are many things that can be blamed for the behavior. Starting with the zipv1.

On a closer look, it appears that, zipv2 is messed up as well. If things are easy to spot for zipv1 Congrats. It is reproducible with any file, and more: it applies to 1 st entry which is not a dir returned by zf.

Looking at the exceptions thrown when attempting to extract files using a wrong password, there are 3 types out of which the last 2 can be grouped together :.

I created an archive file of my own. For consistency's sake, I'll be using it from now on, but everything would apply to any other file as well. Looking at ZipFile. The 1 st raises an exception, so it starts to be clearer why it behaves the way it does. But why the behavioral difference, when attempting to extract items using 2 wrong passwords? As seen in the tracebacks of the 2 different thrown exception types, the answer lies somewhere at the end of ZipFile.

According to [UT. CS]: dmitri-report-f In [5] Biham and Kocher showed that the cipher is weak and demonstrated an attack requiring 13 bytes of plaintext.