Releases: cryptomator/cryptofs
Releases · cryptomator/cryptofs
Release 2.1.0-beta13
- Fix for #111
Release 2.0.1
- Fixed renaming directories/symlinks with shortend names into different, but to be shortened names corrupts structure (#111 )
- Updating to cryptolib 2.0.2 containing upstream fixes
Release 1.9.15
Backport of Fix for #111
Release 2.1.0-beta12
- Adjusted to new API due to hotfix in CryptoLib 2.0.1
Release 2.1.0-beta11
- Redefined public API to read arbitrary claims from unverified vault config
Release 2.1.0-beta10
- Improved health checks (#108, #109, #110)
Added public API to read arbitrary claims from unverified vault configchanged in beta11
Release 2.1.0-beta9
Release 2.0.0
- Adjusted CryptoFS for new CryptoLib API
- Introduces new vault format 8, which stores configuration metadata in
vault.cryptomator(e.g. shortening threshold) - Allows loading of masterkey from sources other than
masterkey.cryptomator - Allows use of GCM for content encryption
- No longer initializes vault root implicitly
- Increase required Java version to 16 (will be bumped to 17 when it becomes GA)
- Removed FileSystemFlags
MIGRATE_IMPLICITLY,INIT_IMPLICITLYandMAX_PATH_LENGTH - Removed CryptoFileSystemProperties
PROPERTY_PASSPHRASE,PROPERTY_PEPPER,PROPERTY_MAX_PATH_LENGTHandPROPERTY_MAX_NAME_LENGTH - Added CryptoFileSystemProperties
PROPERTY_VAULTCONFIG_FILENAME,PROPERTY_KEYLOADER(see #7),PROPERTY_CIPHER_COMBO(see #94) andPROPERTY_MAX_CLEARTEXT_NAME_LENGTH(see #102) - Includes a unique vault id in
vault.cryptomator - Added
module-info.java - Removed
CryptoFileSystemProvider.changePassphrase(...),CryptoFileSystemProvider.exportRawKey(...)andCryptoFileSystemProvider.restoreRawKey(...)(now possible via CryptoLib'sMasterkeyFileAccess) - Replaced
CryptoFileSystemProvider.containsVault(...)withCryptoFileSystemProvider.checkDirStructureForVault(...)
See also milestone 2.0.0
Release 2.0.0-rc5
- Updated dependencies
- Adjusted to latest CryptoLib API