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
Header MAC doesn't match when downloading encrypted files from vault #9916
Comments
Please attach the file {{cyberduck.log}} in the application support directory to have a look at the unhandled application error. |
Replying to [comment:3 dkocher]:
My cyberduck.log file is empty, but I can share the transfer window log:
|
Unfortunately there are still download issues with the latest nightly build (6.0.0.23927), I have updated the error messages and added the transfer and error logs from a fresh test. |
Can you confirm you no longer receive the |
Replying to [comment:6 dkocher]:
The behavior with the large file download has not changed, I still see the |
Unfortunately the behavior with large files still hasn't changed (tested with 6.0.0.23965), I still receive the |
I'm now able to reproduce the issue with large files:
|
Large file downloads are still broken. Transfers now fail after the first 100 MB with the error message: Authentication of chunk 3200 failed.
|
Regression in 39031. |
I can confirm that both my test cases now work perfectly. Thanks a lot for your efforts! |
Replying to [comment:19 ftischhauser]:
|
Thanks to the fixes in [9895] I can now upload to a cryptomator vault on B2 with the latest nightly build. Unfortunately downloads are still failing.
With a small (10MB) file I receive the following error after the download: Transfer incomplete (although the file has been downloaded correctly).
Transfer log:
A large (300MB) file doesn't even start downloading: Unknown runtime application error.
Transfer log:
The cyberduck.log file only contains the following entries:
Could you please give cryptomator on B2 another look? Thanks!
The text was updated successfully, but these errors were encountered: