Download and execute aqr-20261118-win-install.exe if you have no other reason.
User-facing Changes
- Extracting without
-pnow writes only unprivileged extended attributes (user.*on Linux; on macOS everything butcom.apple.system.*andcom.apple.rootless), and says which ones it held back - An archive's mark of the web (Windows' Zone.Identifier, macOS' quarantine) is copied to the files extracted from it, so SmartScreen and Gatekeeper ask about them as they would about the archive
- Encrypted archives (
-P):- Giving a passphrase for an archive that is not encrypted is refused (exit 4)
- A payload cut short right after a chunk now fails (exit 3) instead of being read as a damaged archive
- Large tensor files are written straight to the archive under
-Ptoo
- Windows:
- aqr-win runs on Windows before 10
- The installer's messages match the Windows version (Control Panel or Settings; the note about "Show more options" only on Windows 11)
--stats' JSON now splits each content's archived bytes by stream class- Developer options:
-Z lzmacompresses a batch's streams solid with LZMA-Z together:alwaysmakes whole batches solid, for archives read in full such as self-extracting ones
Specification Changes
- Spacer blocks are allowed in an encrypted archive's payload. Compressors instead must not encrypt a chunk twice under the same nonce
- Repair takes a payload's mirror blocks only from trusted bytes, never replaces a block that authenticates, and treats a payload cut after a chunk as a failure
- Rules for extended attributes that may grant privileges
- aqr_log's message is a UTF-8 string; ill-formed sequences are shown as U+FFFD
Compression Optimizations
- Windows executables (PE):
- x86 jumps are coded as counts of instructions rather than byte offsets
- Base relocations are predicted from the code and the data sections
- Resources of 1 KiB or more are taken as contents of their own, so a resource shared by several images (a program and its language DLLs) is stored once
- The files inside CAB stored folders, RAR (RAR5 and RAR 3.x/4.x), LHA and ALZ archives, and stored entries of RAR, LHA, ALZ and EGG are now recompressed in turn; before, only zstd saw them
- CAB, 7z, RAR, LHA, ALZ, EGG and InstallShield cabinets have their contents worked on one thread each, as ZIP's already were
- A file archived alone now rebuilds streams that pay for a shared module block only together (such as the many small zlib streams of one DLL)
- Very small streams (1 KiB or less in all) are stored as literals in the formula block, not as blocks of their own
Performance Optimizations
- Verifying an encrypted archive decrypts it as it is read rather than all at once
- Smaller Windows binaries:
- aqr.exe 31.4 → 27.5 MB
- The installer 14.8 → 13.1 MB
- The self-extracting stub 542 → 304 KB
- The pack of modules aqr.exe carries 6.9 → 4.7 MB
Bug Fixes
- Names shown on the terminal (listings,
-I, progress, warnings) have control and bidirectional characters escaped - Shell completion for
-Cin bash and PowerShell now quotes directory names; a crafted name could run a command - Temporary spool files and their directory are readable by their owner only (Unix)
- Windows binaries load non-system DLLs only from System32, so a DLL planted next to a downloaded program is never loaded
- Native module code is mapped with each section's own permissions, not read-write-execute
- Windows: sandbox workers run with an AppContainer token and have no network access (Windows 8 and later)
- Self-extracting programs no longer write over existing files or through links and junctions
- Windows 7 target: sandbox workers sometimes failed to start (0xc0000135)
- An append (
-a) that was not committed is now cut off even if it was written in full -Know checks what-dwould extract, and fails where a mirror block differs from a block that decodes- 7z: a wrong passphrase could be accepted for stored folders. Passphrases are now checked by the files' CRCs, and you are warned when there is no CRC to check against
- tar: old GNU sparse members with sizes near 2^64 are rejected
- ZIP: names in archives made on NTFS are split at backslashes
- xz: SHA-256 checks are verified
- When a thread fails to start in a native module run, the tasks already started are joined rather than left running