Cyberduck Mountain Duck CLI

#9956 closed defect (worksforme)

Use memory cached vault password

Reported by: TheBashar Owned by:
Priority: normal Milestone: 6.0.1
Component: cryptomator Version: Nightly Build
Severity: normal Keywords:
Cc: Architecture:


Could you please consider adding an option to cache my vault password(s) in memory. I would prefer not to store my passwords on disk even in the keychain or credential storage. Without storing the password however, the FTP connector in particular prompts me for the vault password on every single upload operation. Ideally I'd like Cyberduck to cache the vault password in memory in some obfuscated or encrypted form which it could decode automatically for every operation. I'd like the UI "disconnect" option to trigger clearing the cached password from memory. Maybe the component for this request should be core? I cannot yet test mounting local vaults, but if it has the same prompt on every transfer behavior, it would be nice there as well.

Change History (2)

comment:1 Changed on May 26, 2017 at 8:37:37 PM by TheBashar

  • Summary changed from Option to cache password in memory to Use memory cached vault password
  • Type changed from enhancement to defect

Maybe this is actually a defect? I just noticed when deleting some test files & folders that I wasn't prompted for the vault password which means it is being cached somewhere. It just seems to be every upload that I get prompted.

comment:2 Changed on May 29, 2017 at 9:19:34 AM by dkocher

  • Component changed from ftp to cryptomator
  • Milestone set to 6.0.1
  • Resolution set to worksforme
  • Status changed from new to closed

We do keep the vault open without the need to reenter the passphrase until you close a browser window. File transfers require you unlock the vault again unless you have chosen to save your vault passphrase in the keychain as they do not share state with the browser session.

Note: See TracTickets for help on using tickets.