VaultSort 2.9.6
encryptionSecuritybug-fix
Fixes folder encryption/decryption failures on Macs with limited internal disk by correcting encrypted temp container sizing arithmetic.
What's New
- Encrypted container preflight now checks free disk against the actual expected write workload instead of the nominal sparseimage cap, accurately reflecting how macOS sparse disk images allocate physical storage on demand
Bug Fixes
- Fixed folder decryption failing with "Could not find secure internal storage" on Macs with moderate free disk — the secure temp directory layer was applying a 1.5x "tar extraction expansion" multiplier on top of the caller's already-inflated 3x size hint, compounding to a 4.5x disk requirement (e.g. a 10 GB encrypted folder demanded 45.5 GB free). Reduced the layer's overhead to 1.05x (HFS+ metadata only), bringing the 10 GB case down to ~31.5 GB
- Fixed
hasCapacitydouble-discounting container size — removed the 0.9x filesystem overhead discount since the container size now already includes the 5% HFS+ margin at creation time - Demoted cross-volume rename (EXDEV) from error to info log level — when decrypting to an external drive, the expected
fs.renamefailure across filesystems was logged as an error despite the copy+delete fallback handling it correctly