[Cyberduck-trac] [Cyberduck] #10352: Not using cryptomator vault

Cyberduck trac at cyberduck.io
Sat Dec 29 20:44:47 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):

 Related to the one above, but slightly different:
 (I created the folder {{{FolderInVault}}} inside the vault using the
 Cyberduck GUI.)
 root at c0072497ea82:/# duck --longlist
 Login successful…
 Listing directory FolderInVault failed.
 Please contact your web hosting service provider for assistance.

 root at c0072497ea82:/# mkdir

 root at c0072497ea82:/# touch

 root at c0072497ea82:/# duck --longlist
 Login successful…
 -rwxr-xr-x      Dec 29, 2018 8:27:20 PM         FileOutsideOfVault.txt
 It appears the CLI only checks the last directory ({{{FolderInsideVault}}}
 or {{{FolderOutsideOfVault}}} respectively). It should however check every
 directory starting with the root directory.

 Note that the issue shown here also affects up- and downloads, when
 operating on an object inside a vault. So while the CLI can
 {{{--download}}} a whole vault, it can not download only a certain folder
 from a vault.

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

More information about the Cyberduck-trac mailing list