Md5sum is not working with S3 on 1.40

[Zetto]

I've upgraded to clone 1.40 and found that md5sum is not working on a crypt remote. It's reporting "UNSUPPORTED" for all files.

I'm running the following command. I get the same result with or without "--fast-list".

rclone md5sum --fast-list --verbose encryptedremote:path

If I go back to 1.38 it returns a blank entry for all files on the encrypted remote.

[ncw (Nick Craig-Wood)]

md5sum has never worked on a crypt remote. At some point rclone became a bit more consistent about showing empty (meaning I don’t have an md5sum for this file) or “UNSUPPORTED” meaning no files have md5sums on this remote.

[Zetto]

I was going off of another thread where cryptcheck was reporting "X hashes could not be checked". The recommendation was to find files that were missing a hash. Now that I reread the post I see the recommendation was to check for a sha1sum and not a md5sum. Unfortunately I see the same output with sha1sum, "UNSUPPORTED".

Cryptcheck reports that a certain number of hashes could not be checked

Can you run rclone sha1sum on the underlying remote? I expect you will see 21 files without SHA1 checksums. How big are those files?

[ncw (Nick Craig-Wood)]

@Zetto

Unfortunately I see the same output with sha1sum, “UNSUPPORTED”.

Alas crypt doesn't support any hashes at the moment

That is why cryptcheck was born.

[Zetto]

Thanks for clarifying @ncw. If I can just sort out the files that are failing to cryptcheck I'll be golden.

How to identify files that can't be cryptcheck

I’m trying to run cryptcheck to compare my local and remote for any issues (e.g. bit rot). If any of my local files have changed I can download them from the remote. I’m using 1.40 and the command I’m running is. rclone cryptcheck --fast-list --verbose /path/to/files encryptedremote:path/to/files When it completes I see the following message. The number varies based on the path that I’m checking. X hashes could not be checked I tried using clone md5sum to identify the files but that’s n…