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
However, the comment only speaks of compression which is not the case for a read-only archive.
Hence, we observed that the stream manipulation in mz_zip_entry_read_close lead to corrupt streams for reads of subsequent enries (mz_zip_entry_read_header fails on the MZ_ZIP_MAGIC_CENTRALHEADER check).
Hence, we observed that the stream manipulation in mz_zip_entry_read_close lead to corrupt streams for reads of subsequent enries (mz_zip_entry_read_header fails on the MZ_ZIP_MAGIC_CENTRALHEADER check).
I'm not sure what the particulars of your zip are. Is it using data descriptors? Can you attach it?
We have the following workflow to read an entry from file
We noticed that
mz_zip_entry_read_close
manipulates the stream if non-NULL args are passedminizip-ng/mz_zip.c
Lines 2104 to 2110 in 55db144
However, the comment only speaks of compression which is not the case for a read-only archive.
Hence, we observed that the stream manipulation in
mz_zip_entry_read_close
lead to corrupt streams for reads of subsequent enries (mz_zip_entry_read_header
fails on theMZ_ZIP_MAGIC_CENTRALHEADER
check).minizip-ng/mz_zip.c
Lines 233 to 234 in 55db144
As a workaround we simply call
mz_zip_entry_close
instead which solves the issue as nowmz_zip_entry_read_close
is called with NULL args.Is it a file issue, an application issue or library issue? Thank you!
The text was updated successfully, but these errors were encountered: