Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use memory cached vault password #9956

Closed
cyberduck opened this issue May 26, 2017 · 2 comments
Closed

Use memory cached vault password #9956

cyberduck opened this issue May 26, 2017 · 2 comments
Labels
bug cryptomator Cryptomator Vault worksforme
Milestone
6.0.1

Comments

@cyberduck
Copy link
Collaborator

b95b27b created the issue

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.
@cyberduck
Copy link
Collaborator Author

b95b27b commented

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.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

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.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug cryptomator Cryptomator Vault worksforme
Projects
None yet
Milestone
6.0.1
Development

No branches or pull requests
1 participant
@cyberduck