[Cyberduck-trac] [Cyberduck] #10715: Cryptomator folder not visible in Cyberduck GUI

[Cyberduck]

#10715: Cryptomator folder not visible in Cyberduck GUI
-------------------------+----------------------
 Reporter:  MarkBlaise   |         Owner:
     Type:  defect       |        Status:  new
 Priority:  normal       |     Milestone:
Component:  cryptomator  |       Version:  6.9.4
 Severity:  normal       |    Resolution:
 Keywords:               |  Architecture:
 Platform:  Windows 8.1  |
-------------------------+----------------------
Description changed by MarkBlaise:

Old description:

> I have been using an encrypted folder named '''Server''' (via
> Cryptomator) on the Wasabi cloud for several months. Works great.
>
> I now want to create two subfolders:[[BR]]
>
> Server\Full\[[BR]]
>
> Server\Diff\
>
> In the Cyberduck GUI, I first tried creating Full and Diff as "normal"
> folders in the Server vault, thinking that they would also be encrypted
> because they are already in a vault. They were created as subfolders of
> Server, but were not encrypted - I could see the files copied into those
> folders from the Wasabi Console.
>
> So, again, in the Cyberduck GUI, I deleted the two subfolders and then
> created them as Crytpomator vaults, again as subfolders of the Server
> folder (which is a vault).
>
> The Cyberduck GUI does not display the new Full and Diff vaults in its
> UI, so I can't access files in them from the GUI. From the Wasabi console
> I can see the Full and Diff folders in the Server folder. and inside
> these new vaults I see a folder named '''d''' and a file named
> '''master.cryptomator''', as expected.
>
> I use the Duck CLI to upload backups to the cloud in automated
> (unattended) scripts on a Windows 8.1 box. When I use the CLI
> interactively to access the new vaults, it prompts me for the password.
> This works, so the folders are there, but I can't see them in the GUI.
>
> Also, the batch processes uploading the backups freeze because the CLI is
> waiting for a password to be entered. This means that the CLI is not
> adding the passwords to the password keychain. The CLI parameter
> --nokeychain would imply otherwise.
>
> If I can avoid it, I really don't want to pass the password on the
> command line (via -p or --password) because that means putting the
> password in the clear in batch scripts.
>
> Is there a way to add the password to the keychain from the CLI?
>
> Why does the Cyberduck GUI not display the new vaults?
>
> Please advise.

New description:

 I have been using an encrypted folder named '''Server''' (via Cryptomator)
 on the Wasabi cloud for several months. Works great.

 I now want to create two subfolders:[[BR]]

 Server\Full\[[BR]]

 Server\Diff\

 In the Cyberduck GUI, I first tried creating Full and Diff as "normal"
 folders in the Server vault, thinking that they would also be encrypted
 because they are already in a vault. They were created as subfolders of
 Server, but were not encrypted - I could see the files copied into those
 folders from the Wasabi Console.

 So, again, in the Cyberduck GUI, I deleted the two subfolders and then
 created them as Crytpomator vaults, again as subfolders of the Server
 folder (which is a vault).

 The Cyberduck GUI does not display the new Full and Diff vaults in its UI,
 so I can't access files in them from the GUI. From the Wasabi console I
 can see the Full and Diff folders in the Server folder. and inside these
 new vaults I see a folder named '''d''' and a file named
 '''master.cryptomator''', as expected.

 I use the Duck CLI to upload backups to the cloud in automated
 (unattended) scripts on a Windows 8.1 box. When I use the CLI
 interactively to access the new vaults, it prompts me for the password.
 This works, so the folders are there, but I can't see them in the GUI.

 Also, the batch processes uploading the backups freeze because the CLI is
 waiting for a password to be entered. This means that the CLI is not
 adding the passwords to the password keychain. The CLI parameter
 --nokeychain would imply otherwise.

 If I can avoid it, I really don't want to pass the password on the command
 line (via -p or --password) because that means putting the password in the
 clear in batch scripts.

 Is there a way to add the password to the keychain from the CLI?

 Why does the Cyberduck GUI not display the new vaults?

 Please advise.

 '''NOTE:''' I don't think this should matter, but the "sub-vaults" (Full
 and Diff) were given the same password as the parent vault (Server)

 '''CORRECTION'''

 I now realize that the duck CLI -p command line parameter is for the S3
 ACCOUNT password, not the password that will unlock the vault.

 So there is no way to access a vault by the CLI unless the vault password
 is in the keychain. And I can't get the password into the keychain because
 the Cyberduck GUI doesn't display them.

 ''Is there another way to get the vault passwords into the keychain?''

 So, there's no way to access these new folders.

 Is it possible that nested vaults are not supported? The Wiki doesn't seem
 to say anything about that.

 Or did creating these folders as normal, deleting them, and then creating
 them as vaults by the same name - could that be the issue?

--

--
Ticket URL: <https://trac.cyberduck.io/ticket/10715#comment:1>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows