You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Old minizip (1.1 with zip64 patch) was able to generate zip files that have more than 65535 entries without switching to zip64 mode. So result zip doesn't have ZIP64 central directory. At the same time it wasn't giving any errors and was able to fully read it afterwards. I understand that this is considered to be improper zip, but is it possible to read such files with new minizip-ng?
I had to omit format sanity check to read all entries without errors (replaced with err = MZ_OK;
Is there some better way? Can it be added as option? I also tried using "recover" flag but it was still giving error.
Here is an example of such file (65536 entries of empty files): corrupted_65536_entries.zip
The text was updated successfully, but these errors were encountered:
Old minizip (1.1 with zip64 patch) was able to generate zip files that have more than 65535 entries without switching to zip64 mode. So result zip doesn't have ZIP64 central directory. At the same time it wasn't giving any errors and was able to fully read it afterwards. I understand that this is considered to be improper zip, but is it possible to read such files with new minizip-ng?
I had to omit format sanity check to read all entries without errors (replaced with err = MZ_OK;
minizip-ng/mz_zip.c
Line 1038 in 99d3901
Is there some better way? Can it be added as option? I also tried using "recover" flag but it was still giving error.
Here is an example of such file (65536 entries of empty files):
corrupted_65536_entries.zip
The text was updated successfully, but these errors were encountered: