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

Automatically open Cryptomator safes in Cyberduck without refresh #10418

cyberduck opened this issue Aug 5, 2018 · 1 comment

Automatically open Cryptomator safes in Cyberduck without refresh #10418

cyberduck opened this issue Aug 5, 2018 · 1 comment


Copy link

@cyberduck cyberduck commented Aug 5, 2018

eada457 created the issue

  1. Create a new Cryptomator safe by right click > new encrypted safe and enter password
  2. Open the folter of the created safe (here test)
  3. Now you see the content of the safe folder as it is in OneDrive with masterkey.cryptomator file
  4. After refreshing using F5, some popup appears which ask for the safe credentials
  5. Only now we see the content of our safe

-Open .cryptomator files as safe*

I also tried to double click on the masterkey.cryptomator file after step 3 instead of hitting F5. In this case, Cyberduck mounts the safe. But when using multiple safes, I got an dialog that ask me to overwrite masterkey.cryptomator. This seems issued to the fact that Cyberduck download the file to my Downloads folder. So after opening the first safe, there is an existing file from the first safe.

-Expected behaviour/Suggestion*

So my suggestion is to change Cyberducks behaviour like this: When opening a folder, Cyberduck should look for files called masterkey.cryptomator. If those file is present, we have a Cryptomator safe and Cyberduck should try to open it (displaying the password dialog if required).

I'm using Version 6.6.3 (28581) on Windows 10 x64.

Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 21, 2018

@dkocher commented

Please make sure you have selected Preferences → Cryptomator → Auto detect and open vault in browser.


@cyberduck cyberduck closed this Aug 21, 2018
@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.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant