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 am unsure how Cyberduck implements renaming. 3 questions:
rename file: is the object simply renamed, or is it copied to the new name and the original deleted?
rename folder: same question ... plus, if copy/delete, does this rewrite all the files in the folder into the new folder?
rename Cryptomator vault: same question, though Renaming vault decrypts all files prior rename #10131 (almost 2 years old) seems to indicate that all contained files are decrypted and moved into an unencrypted folder. Is this accurate/reproduced?
Thanks
The text was updated successfully, but these errors were encountered:
Files and folders are renamed if the protocol supports such operations such as SFTP or WebDAV. When a rename operation is not supported we copy and and then delete the origin file. This is the case for S3. In these cases we have to recursively copy containing files when renaming a folder.
I am unsure how Cyberduck implements renaming. 3 questions:
rename file: is the object simply renamed, or is it copied to the new name and the original deleted?
rename folder: same question ... plus, if copy/delete, does this rewrite all the files in the folder into the new folder?
rename Cryptomator vault: same question, though Renaming vault decrypts all files prior rename #10131 (almost 2 years old) seems to indicate that all contained files are decrypted and moved into an unencrypted folder. Is this accurate/reproduced?
Thanks
The text was updated successfully, but these errors were encountered: