Reading "disk number start"

[kalibera]

Minizip reads the disk number start from the zip64 extended information extra field, when the value of disk_num_start is 0xffffffff (MAXU32). However, the specification seems to be saying that one should read from the extra field when the value is 0xffff (4.4.13). Is my reading of the specification correct?

https://github.com/madler/zlib/blob/21767c654d31d2dccdde4330529775c6c5fd5389/contrib/minizip/unzip.c#L1062 https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT

I don't have any use case/archive for this, just came across this possible inconsistency in the code while analyzing a bug report.

[madler]

You are correct. I will leave it to @gvollant to suggest a fix.

[gvollant]

you are right, unz64local_getShort is used to fill disk_num_start

[madler]

Applied fix.

[madler]

Applied fix manually. (Due to indentation issues.)