5b5

It turned out the problem occurs when the first file in the archive is an empty directory. The call to unzReadCurrentFile in this case will be given a len parameter...

Tried to fix the problem by skipping over directories, i don't know enough about Zipfiles to be sure i didn't miss any cases. (i.e. is it 100% safe to read...

Another solution might be just to check for readBytes > 0 ... `` if (readBytes < 0) { ... return NO; } else if (readBytes > 0) { return YES;...

Sorry, i must ask you for some patience, i will not be able to review your comments and respond for the next two weeks. I will try to respond asap...

Thanks for fixing the memory issues! I reproduced and tracked down the problem today, this is what i found: 1.) The problem is not reproducible in v2.1.4 because `unzOpenCurrentFilePassword` returns...

for unit tests and test files see https://github.com/5b5/ZipArchive/commit/2a4144cca2f3f9dce4da98038b91e993c2362809 If you think the behavior described in 1.) above is correct, please close this PR.

As i described above, when a password-encrypted zip file is generated by SSZipArchive it will differ from an encrypted archive zipped from command line (even in 2.1.4) in having the...