From bfdd5e2c226331e8b3c4379fc51149cf9067c91f Mon Sep 17 00:00:00 2001 From: Nick Craig-Wood Date: Fri, 11 Jul 2025 14:14:18 +0100 Subject: [PATCH] filescom: document that hashes need to be enabled - fixes #8674 --- docs/content/filescom.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/content/filescom.md b/docs/content/filescom.md index 2a718a7a5..95acf3339 100644 --- a/docs/content/filescom.md +++ b/docs/content/filescom.md @@ -99,6 +99,21 @@ excess files in the directory. rclone sync --interactive /home/local/directory remote:dir +### Hashes + +In December 2024 `files.com` started [supporting more checksums](https://www.files.com/blog/2024/11/01/new-modern-checksum-options-now-available-with-opt). + +However if you want hashes you **must** enable them in your site by +visiting the "File Integrity" section in "Data Governance" to +configure your settings and select the checksum algorithms that meet +your requirements. + +Rclone currently only support CRC32 and MD5 for use in syncing but +selecting more checksums will not affect rclone's operations. + +For use with rclone, selecting at least MD5 is recommended so rclone +can do an end to end integrity check. + {{< rem autogenerated options start" - DO NOT EDIT - instead edit fs.RegInfo in backend/filescom/filescom.go then run make backenddocs" >}} ### Standard options