Cryptomator is saving password in keychain when setting is off

[moisesrodriguez]

I've been having issues that Mountain Duck would not prompt for Cyptomator password to unlock vault. After looking at discussions to remove password from Keychain I noticed that there was indeed a password there even I never activated it. After I deleted the password Mountain Duck prompted finally for the password, but I noticed that it again saved the password in Keychain.

[yhay81]

This is a confirmed application bug, not a misunderstanding of the setting. The exact issue has already been fixed on master.

The faulty path is in PasswordVaultLoader. The passphrase dialog returned a Credentials object containing both the password and the state of the Save Password checkbox, but the old code copied only getPassword() into a new VaultCredentials. It discarded the checkbox state. The new vault credentials could therefore still be treated as saved, and the loader then wrote Cryptomator Passphrase (...) to Keychain.

Commit 59ab388 — Copy save flag from prompt fixes both the initial unlock and retry paths by doing the equivalent of:

credentials = new VaultCredentials(input.getPassword());
credentials.setSaved(input.isSaved());

The project's current CHANGELOG lists this verbatim under the upcoming 9.5.3 section: “Password saved regardless of checkbox selection (Cryptomator)”. At the moment the repository's latest release tag is still release-9-5-2, so the changelog entry is ahead of the latest tagged Cyberduck release. Because Mountain Duck shares this core vault code, the Mountain Duck build you are running also needs to incorporate commit 59ab388 (or a later shared-core revision); do not assume that seeing the 9.5.3 changelog means your installed Mountain Duck already contains it.

For now:

1. Check Mountain Duck → About and include the exact version/build in this Discussion.
2. Keep the Save Password option off.
3. After disconnecting the affected bookmark, remove the Cryptomator Passphrase (...) entry from macOS Keychain Access again. On an affected build it will be recreated after every successful vault unlock, so this is only a temporary cleanup, not a permanent workaround.
4. Update to the first Mountain Duck release/build whose release notes include this fix. After updating, delete the old Keychain item once, reconnect, leave Save Password unchecked, disconnect, and verify that the item was not recreated.

The stored value is in macOS Keychain rather than a plain-text preference file, but the behavior still violates the checkbox and should be treated as a credential-retention bug. Reinstalling or repeatedly deleting the item cannot fix the old code path; updating to a build containing 59ab388 is the actual fix.