You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Cryptomator vault named Server. It has many files in it that can be accessed via the Cyberduck GUI or the Duck CLI.
I created 2 folders in the Server vault via the File-New Folder menu option in Cyberduck, named Diff and Full. My assumption is that these new subfolders and the files in them are encrypted by Cryptomator - is that correct?
Using CyberDuck, I uploaded a few files into the new sub folders. As expected, Cyberduck displays these files (see screen shot SubFolders.jpg).
I then uploaded another file into the Diff subfolder via the Duck CLI. This file, named 20190531-080759-D_B2D000177.bkf, does not appear in the Cyberduck GUI listing of the Diff folder. You can see this in the attached screen shot referenced above.
Furthermore, when I use the Duck CLI to display a listing of the Diff subfolder, the listing contains ONLY the file uploaded by the CLI:
C:\Users\Mark>duck -l wasabisys://T5ZHIOV9VGMNBAKU1HQ4@Blaise-Backup/Server/Diff/
log4j:WARN No appenders could be found for logger (ch.cyberduck.core.preferences.Preferences).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Login successful?
20190531-080759-D_B2D000177.bkf
When I use the Duck CLI to display a listing of the Full subfolder I'm told "file not found" - that is, the Full subfolder does not exist:
C:\Users\Mark>duck -l wasabisys://T5ZHIOV9VGMNBAKU1HQ4@Blaise-Backup/Server/Full/
log4j:WARN No appenders could be found for logger (ch.cyberduck.core.preferences.Preferences).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Login successful?
File not found. /Blaise-Backup/Server/Full. Please contact your web hosting service provider for assistance.
Lastly, when I look at the Server vault in the Wasabi Console (the console just lists files and folders via web browser), I see the Diff subfolder and no Full subfolder. And I can traverse into the Diff subfolder and see the 20190531-080759-D_B2D000177.bkf file in the clear (not encrypted). I downloaded this file via the Wasabi Console and it is identical to the original - clearly not encrypted.
In b5061fd. We have introduced an explicit argument to reference the vault. Use --vault /home/folder/vault/ in conjunction with --upload to unlock the vault prior an upload.
I have a Cryptomator vault named Server. It has many files in it that can be accessed via the Cyberduck GUI or the Duck CLI.
I created 2 folders in the Server vault via the File-New Folder menu option in Cyberduck, named Diff and Full. My assumption is that these new subfolders and the files in them are encrypted by Cryptomator - is that correct?
Using CyberDuck, I uploaded a few files into the new sub folders. As expected, Cyberduck displays these files (see screen shot SubFolders.jpg).
I then uploaded another file into the Diff subfolder via the Duck CLI. This file, named 20190531-080759-D_B2D000177.bkf, does not appear in the Cyberduck GUI listing of the Diff folder. You can see this in the attached screen shot referenced above.
Furthermore, when I use the Duck CLI to display a listing of the Diff subfolder, the listing contains ONLY the file uploaded by the CLI:
When I use the Duck CLI to display a listing of the Full subfolder I'm told "file not found" - that is, the Full subfolder does not exist:
Lastly, when I look at the Server vault in the Wasabi Console (the console just lists files and folders via web browser), I see the Diff subfolder and no Full subfolder. And I can traverse into the Diff subfolder and see the 20190531-080759-D_B2D000177.bkf file in the clear (not encrypted). I downloaded this file via the Wasabi Console and it is identical to the original - clearly not encrypted.
PLEASE ADVISE.
Attachments
SubFolders.jpg
(162.5 KiB)The text was updated successfully, but these errors were encountered: