[Cyberduck-trac] [Cyberduck] #10352: Not using cryptomator vault
Cyberduck
trac at cyberduck.io
Sat Dec 29 20:05:43 UTC 2018
#10352: Not using cryptomator vault
------------------------------------------+-------------------------
Reporter: dennis | Owner: dkocher
Type: defect | Status: assigned
Priority: high | Milestone: 7.0
Component: cli | Version: 6.5.0
Severity: normal | Resolution:
Keywords: cli cryptomator google drive | Architecture:
Platform: |
------------------------------------------+-------------------------
Comment (by sebastian):
Another case of ''not using cryptomator vault'' happens when listing
directories inside a vault:
{{{
root at c0072497ea82:/# touch /mnt/hostdata/CryptomatorVault/x.txt
root at c0072497ea82:/# ls -l /mnt/hostdata/CryptomatorVault/
total 1
drwxrwxrwx 2 root root 0 Dec 29 19:23 d
-rwxr-xr-x 1 root root 327 Dec 29 19:23 masterkey.cryptomator
-rwxr-xr-x 1 root root 0 Dec 29 19:54 x.txt
root at c0072497ea82:/# duck --longlist
file:///mnt/hostdata/CryptomatorVault/
Login successful…
drwxrwxrwx Dec 29, 2018 7:23:58 PM d
Unlock Vault. Provide your passphrase to unlock the Cryptomator Vault
“CryptomatorVault“.
Passphrase:
-rwxr-xr-x Dec 29, 2018 7:26:18 PM test.txt
}}}
Note that the folder {{{d}}}, that is an internal structure of the vault,
is displayed while the file {{{x.txt}}} is not. {{{test.txt}}} is
correctly displayed because it is a file inside the vault.
It appears that the CLI treats the folder to be listed as a normal folder
and lists its contents until it finds a {{{masterkey.cryptomator}}} at
which point it asks for the password and treats the folder as a vault. It
should rather check at first whether the folder is a vault, e.g. whether
it contains a {{{masterkey.cryptomator}}}.
--
Ticket URL: <https://trac.cyberduck.io/ticket/10352#comment:5>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows
More information about the Cyberduck-trac
mailing list