-
-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keeps uploading files unencrypted to Wasabi if the connection is interrupted and then resumed without exiting. #15643
Comments
Just to add to this, I don't know if you can see from the logs. But Cyberduck, when you press the stop button- nothing happens. The transfer will stop but the transfer just pauses, there is no confirmation it's been stopped. So this results in having to force quit in order to clean up transfers from recent activity. |
Lastly, apologies if this is a feature request along with a bug, but wound it be at all possible to prompt users if they’ve enabled Cryptomator that they are about to transfer files in an unencrypted state? Since client-side encryption is one of the defining features of Cryptomator it’s would be awesome to make sure there are no leaks. thanks! |
This is also reproduced by a failed download, force quitting and chosing "reload" will also upload the files outside of the vault and in unencrypted format even with the vault currently unlocked in Cyberduck... |
Describe the bug
This has happened at least ten times the past week. I'm not sure if the bug log captures this, but whenever there is an interruption in connection and "continue anyway" or sometimes "reload" is selected- files are uploaded unencrypted outside the vault in Wasabi. This is really concerning for me as A, I might not always notice it, and also due to the fact that if versioning or compliance period is setup with Wasabi, I have to wait that length of time to delete the unencrypted files from storage.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect that for whatever reason the connection failed, that "continuing" would force a reconnection and again unlock the vault automatically or during that process (since it's reconnecting anyways?) rather then continue uploading files without re-establishing the vault status.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Log Files
I've attached the log files and redacted sensitive information.
cyberduck_text_fully_redacted.txt
The text was updated successfully, but these errors were encountered: