How can we protect encrypted files and directories from being fingerprinted when stored on online storage services?

Assuming that online storage providers are considered untrusted, if files and directories are encrypted, how can these be protected against fingerprinting?

The files are encrypted using rclone’s implementation of Poly1305 and XSalsa20 before being backed up to the cloud provider.

According to rclone’s documentation, the available metadata is file length, file modification date and directory structure.

  • What can be identified?
  • What can be inferred?
  • What attack vectors are there against the encrypted files and directories if the online storage provider is compromised assuming the passphrase is at least 24 characters long and is a combination of alphanumeric and special characters (uppercase and lowercase) as well as salted with similar entropy?

The encrypted data is considered to be sensitive.

How can I protect those files from being fingerprinted and the contents inferred such as ownership, source and the like?

Browser that cannot be fingerprinted? [duplicate]

This question already has an answer here:

  • How to fight browser fingerprinting? 7 answers

I was using Tor Browser (some kind of Firefox) which is supposed to be immune to fingerprinting, but when I visited I was surprised to see that every time I changed the identity their fingerprint ID remained the same! And I didn’t allow canvas image data or anything.

How is that possible?

Does this mean there’s no way to avoid fingerprinting?