-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zipfile signature not read #40
Comments
Actually there is a slight difference this result in an: Error: invalid block type if read through unzip. The signature itself seems to be read correctly. |
I just ran into this on a few large zip files I was parsing with node-excel. It appears the signature is being read, however - any ideas on this? I haven't been able to get it to work simply by skipping the signature. |
Ran into this same issue today with Unzip. Trace:
|
Anyone learn any more about this issue? I just tried to to use node-unzip on this zip file and it's not a signature problem (parse.js confirmed that the file's signature was 0x04034b50), but it still blows up with "invalid stored block lengths". |
It sounds like the "block lengths" and "block types" errors might be separate issues. I'm working with a 3.5 MB zip file. When I use the Mac OSX compression tool to create the zip (right click on a folder and click Compress), then run it through node-unzip, I get "invalid stored block lengths". When I compress the same directory using the Maybe the storage format has some variations that we're not accounting for. I did a hex diff of the two files. I don't know if it's helpful to a keener eye than mine: |
I am getting the same issue with Says
while extracting an .ipa file generated from Xcode 6.1. This was working fine for iOS 7 IPAs but started breaking for iOS 8 IPAs |
+1 on this; also encountering this issue ( |
Anyone has any hints what this error means? |
The problem is in parse.js. If you uncomment setImmediate in 161 than it works on my machine. And it seems logical. There is no need to wait for I/O events to finish. Actually that additional I/O events are executed is causing the problem. // setImmediate(function() { I'm using the latest version. |
Just had the same issue. Thanks for the fix @jdonnerstag. Unfortunately I do not see a PR for this change. :( |
+1 |
I had the same issue. Switching to node-unzip-2 fixed it for me. |
Referencing this issue nodejs/node-v0.x-archive#6384 here as it started out with me trying to use unzip with a github repo release zipfile
Summary: any release zipfile from a github repositiory will not work correctly by just piping the stream to unzip, e.g. as per example.
fs.createReadStream('path/to/archive.zip').pipe(unzip.Extract({ path: 'output/path' }));
As tjfontaine demonstrated in the response to issue the signature has to be read from the stream first before piping stuff to unzip.More background on the signature: https://users.cs.jmu.edu/buchhofp/forensics/formats/pkzip.html
The text was updated successfully, but these errors were encountered: