Skip to content

@github-actions github-actions released this Jun 22, 2020 · 15 commits to develop since this release

  • Allow access to vaults on read-only drives (#1173)
  • Added size-based log rotation (#1141)
  • Fixed issue preventing application start (#1254)
  • Fixed race condition leading to invalid file contents being displayed (cryptomator/cryptofs#85)
  • Fixed memory leak (#1249)

📜 A complete list of closed issues is available here.

Assets 11

@github-actions github-actions released this May 27, 2020 · 23 commits to develop since this release


📜 A complete list of closed issues is available here.

Assets 11

@github-actions github-actions released this May 12, 2020 · 48 commits to develop since this release

  • Improved unlock workflow (#1088, #1083)
  • Added option to reveal directory containing logs (#1184)
  • Improved response to changing conditions regarding vault state (#1139, #1110, #1190)
  • Changing a password now also affects stored passwords (#1189), kudos to @purejava
  • Fixed unresponsive UI on certain Linux distros (#1167)
  • Fixed access to system keychain on Linux (#1169), kudos to @purejava and @swiesend

📜 A complete list of closed issues is available here.

Assets 11

@github-actions github-actions released this Apr 30, 2020 · 68 commits to develop since this release

  • Fixed data inconsistencies and memory leaks (#1131)
  • Fixed masterkey restoration when using recovery key (#1163)
  • Improved performance for filename encryption/decryption

📜 A complete list of closed issues is available here.

Assets 11

@github-actions github-actions released this Apr 29, 2020 · 78 commits to develop since this release

This update restores and improves compatibility of vaults stored in locations that limit file path or filename lengths, such as WebDAV drives on Windows or eCryptfs-encrypted volumes on Linux, further details here.

  • Fixed problems with vaults stored in locations that support limited file path and/or filename lengths (#1116, #1134, #1144)
  • Vaults can now be created/added that were falsely detected as duplicates (#1115)
  • Drive letters A: and B: are now excluded on Windows (#1123)
  • Password fields can now be cleared with Ctrl/Cmd + Backspace (#885)

📜 A complete list of closed issues is available here.

Assets 11

@github-actions github-actions released this Apr 21, 2020 · 111 commits to develop since this release

  • Unofficial support for Windows 7 SP1+
  • Don't stop migration when handling too many conflict files (#1124)
  • Conceal password field when starting long-running tasks (#1126)
  • Improved error handling when dealing with malformed masterkey files
  • Start application even if settings file is malformed/corrupted
  • Migrated to JDK 14 and GitHub Actions 🙂

📜 A complete list of closed issues is available here.

Assets 11

@cryptobot cryptobot released this Apr 16, 2020

Cryptomator

Cryptomator has been redesigned and comes with a new dark mode. It is not simply a redesign, it was a full rewrite of the UI. During the rewrite, a whole new code structure was planned which makes it easier to extend the application in the future. One goal of the redesign was to make the onboarding process easier for users who don't feel too comfortable with encryption software. Usability tests helped designing the workflows and understanding common misconceptions. Besides the redesign, the new vault format 7 increases compatibility with some cloud services and at the same time reduces the complexity for certain I/O operations.

To support the ongoing open-source development of Cryptomator, consider buying a donation key, which unlocks the new dark mode. ❤️

What's New

  • Introduced vault format 7 (#625, #891)
    • Ciphertext file layout has been redesigned (see Security Architecture / Filename Encryption)
    • Filenames are encoded with base64url so that name shortenings are less likely
    • Note: When upgrading a vault from an older version of Cryptomator, you have to upgrade the vault to the latest version, which is not backwards-compatible
  • Redesigned UI (#808, #925, #926)
    • Added themes, incl. dark mode theme (#930)
    • Improved workflows, incl. unlock vault (#928, #939), add vault (#929), change password (#621, #927), vault settings (#931)
    • Improved password fields (#458)
    • Various usability improvements (#341, #346, #396, #850, #932)
  • Improved tray menu
    • Added vault list (#225)
    • Added "unlock and lock" per vault (#297)
    • Added "lock all vaults" (#863)
  • Added recovery keys, making it possible to reset a vault's password (#1060)
  • Added compatibility checks for underlying filesystem (#1056)
  • Added "auto-start" setting on Windows and macOS (#418)
  • Added "start hidden" setting (#62, #283, #346, #418, #957, #1035, #1040)
  • Added -Dcryptomator.minPwLength configuration variable to set minimum password length (#1018)
    • Default is set to 8 for GDPR compliance
  • Improved termination handler to automatically lock vaults (#838, #970, #980)
  • Improved update checker (#272)

Bugfixes

  • Fixed compatibility with certain Google Drive sync clients, where renaming long filenames into short ones didn't work (#891)
  • Fixed high CPU usage under certain conditions (#129, #186, #827, #849, #881)
  • Fixed duplicates in vault list (#1032)

Windows

  • Fixed slow writing in Dokany (#960)
  • Fixed GUI freeze (#984)

macOS

  • Removed "keystroke receiving" prompt on macOS Catalina (#986)
    • Note: This permission has never been used and was an upstream bug in JavaFX
  • Fixed crash on macOS Catalina when file chooser dialog was shown (#1062)
  • Fixed usage of FUSE when device is offline (#1038)
  • Support for more than three simultaneous mounts with FUSE (#674)

Linux

  • Fixed excessive RAM and CPU usage with certain versions of Mesa (#369, #953)
  • Support for more than three simultaneous mounts with FUSE (#674)

📜 A complete list of closed issues is available here.

Assets 11
Pre-release
Pre-release

@cryptobot cryptobot released this Apr 14, 2020

This is the third release candidate for our upcoming version 1.5.0 of Cryptomator.

See 1.5.0 for detailed release notes.

⚠️ Only upgrade your vault to the new format after making backups. While we are not aware of any bug right now, keep in mind this is a pre-release version intended for testing!

Assets 8
Pre-release
Pre-release

@cryptobot cryptobot released this Mar 26, 2020

This is the second release candidate for our upcoming version 1.5.0 of Cryptomator.

See 1.5.0 for detailed release notes.

⚠️ Only upgrade your vault to the new format after making backups. While we are not aware of any bug right now, keep in mind this is a pre-release version intended for testing!

Assets 8
Pre-release
Pre-release

@cryptobot cryptobot released this Mar 12, 2020

This is the first release candidate for our upcoming version 1.5.0 of Cryptomator.

See 1.5.0 for detailed release notes.

⚠️ Only upgrade your vault to the new format after making backups. While we are not aware of any bug right now, keep in mind this is a pre-release version intended for testing!

Assets 8
You can’t perform that action at this time.