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
Add SHA1 or other verification for BackBlaze B2 #9733
Comments
I checked the source for b2 meanwhile but I can only see that the code retrieves the SHA1 that Backblaze gives, and parses it.[[br]] 7-zip's SHA1 calculation takes 22 seconds on the same machine.[[br]] I also read the wiki about the Synchronize feature that SHA comparison is supported for S3.[[br]] |
I think this wiki article also needs some refresh:[[br]] |
Well, upon further testing, LARGE FILES (have no idea what they call large) have NO SHA1 sum.[[br]]
[[br]][[br]] |
We do include the checksum in every
The checksum is calculated in |
If you upload a file that is transferred as a large upload it will not be visible to synchronize when interrupted. Please restart the upload to resume a large file upload. |
That was blazing fast, thank you! |
Milestone renamed |
CyberDuck Version: 5.2 (Beta)
-*Why mark this as defect, and not a new feature:**[[br]]
Because the current "only timestamp comparison" renders the entire b2 upload feature useless.
-What happens:*
You have to enable TIMESTAMP for Uploads.[[br]]
(I think this should be enabled by default.)[[br]]
Upload a folder using Synchronize or with Upload.[[br]]
Stop transfer half-way.[[br]]
Upload same folder using Synchronize[[br]]
Only the timestamp will get checked.[[br]][[br]]
What should happen:
Upload a folder using Synchronize, OR by hand.[[br]]
The client should calculate SHA1sum and verify with local files.[[br]]
IF file differs: transfer.[[br]]
Then, no timestamp would be even needed.[[br]]
-*THE PROBLEM:**[[br]]
The current way is no way to transfer files.[[br]]
Backblaze provides a 99.99+% redundancy, and the client provides a 50% chance of getting your files up there safely. [[br]]
I mean, yes it may get uploaded, but we have no idea what the file ended up be. [[br]]
Here and there bits may be missing.[[br]]
And in my case, with a 1gbps server, the transfer got stuck a few times. [[br]]
With timestamps, I was able to "continue", but I have no idea if the files that ended up in B2 are MY files, or some damaged binaries.[[br]][[br]]
-*How to implement:**[[br]]
Well, Java has SHA1 calculation included. [[br]]
For Backblaze B2: https://www.backblaze.com/b2/docs/b2_get_file_info.html [[br]]
Compare both, if it does not match, delete file on B2, and restart transfer.
The text was updated successfully, but these errors were encountered: