--crypt-no-data-encryption (no_data_encryption) meaning explanation


Option to either encrypt file data or leave it unencrypted.

I've been reading carefully through the documentation, but I can not find what do you mean by "file data".

  1. So, what is "file data" in your context? Is it a file's metadata?

  2. Why it is "False" by default? Is it cpu, storage or memory expensive?

  1. the contents of the file.
  2. false -> Encrypt file data
    the flag name is confusing as it being a negative.
    so if you do not use the flag, then rclone will crypt the contents of the file.

perhaps the flag should be
and the default is true

i think the following is correct.
in the beginning, of the rclone timeline, rclone always crypted the contents of the files; no choice not to crypt the contents of the file.
then some fellow rcloner requested to only crypt the folder names and/or file names and not the contents.
so --crypt-no-data-encryption, a confusing awkwardly named flag was created.
which could be useful if you wanted to use the encryption of the cloud provider, not rclone's version.

for example, with aws s3 and its many clones, you can crypt the file contents but cannot crypt folder names and file names.
so by using --crypt-no-data-encryption=true to crypt the folder names and file names but not the contents.
and the encryption of the file contents will use aws s3 encryption

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.