#zip64 — Public Fediverse posts

In short: if you have any file in your app (or whatever it is you’re trying to get Apple to sign) that is over 4 GiB, you must use a disk image (DMG) to package it for notarytool, not a zip file.

This is because support for files larger than 4 GiB requires using the “Zip64” zip file format, which would be fine except Apple’s notary servers can’t handle them. If you give them such a zip file, […]

I would rather NOT rewrite our .zip archive code to do the «unpack in separate directory and then remove» thing. So does anybody know of a different C++ library to access zip archive contents directly that DOES support #Zip64?

#askFedi #fediHelp #CPlusPlus #askMastodon #mastoHelp

I would rather NOT rewrite our .zip archive code to do the «unpack in separate directory and then remove» thing. So does anybody know of a different C++ library to access zip archive contents directly that DOES support #Zip64?

#askFedi #fediHelp #CPlusPlus #askMastodon #mastoHelp

Oh well that's just peachy. #EUMETSAT switched to #Zip64 for its zipped data archives even when standard zip worked fine (I assume for consistency with situations where it didn't?), and #Zipios, the C++ library we're using to access the file inside the zip without unpacking the archive, does not support Zip64.

Oh well that's just peachy. #EUMETSAT switched to #Zip64 for its zipped data archives even when standard zip worked fine (I assume for consistency with situations where it didn't?), and #Zipios, the C++ library we're using to access the file inside the zip without unpacking the archive, does not support Zip64.

#libzip 1.11.4 has been released (#LZMA / #ZIP / #Zip64 / #zstd / #Zstandard / #bzip2 / #AES / #PKWARE / #FileArchiver / #DataCompression) https://libzip.org/

#libzip 1.11.4 has been released (#LZMA / #ZIP / #Zip64 / #zstd / #Zstandard / #bzip2 / #AES / #PKWARE / #FileArchiver / #DataCompression) https://libzip.org/

@nicklockwood The reason why Apple doesn't set this information is, I suspect, because they can compress > 4 GB of data into a single stream, something that's officially not supported by original zip, and that's why some other zip tools can't uncompress Apple-generated zip files with data > 4 GB in them (it's a smart work-around the problem to support the #zip64 standard, which isn't very popular). However, Apple's zip should still set these header values if they can, but they don't :(

@nicklockwood The reason why Apple doesn't set this information is, I suspect, because they can compress > 4 GB of data into a single stream, something that's officially not supported by original zip, and that's why some other zip tools can't uncompress Apple-generated zip files with data > 4 GB in them (it's a smart work-around the problem to support the #zip64 standard, which isn't very popular). However, Apple's zip should still set these header values if they can, but they don't :(

Watch Attile Szűcs' talk on 𝗛𝘂𝗴𝗲 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝘀 𝗶𝗻 @libreoffice and hear about the capabilities and challenges of the #Zip64 support implementation.

#CollaboraOnline #COOLdays #opensource

https://youtu.be/GZPmcpfXIhg

Watch Attile Szűcs' talk on 𝗛𝘂𝗴𝗲 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝘀 𝗶𝗻 @libreoffice and hear about the capabilities and challenges of the #Zip64 support implementation.

#CollaboraOnline #COOLdays #opensource

https://youtu.be/GZPmcpfXIhg