Recommended Crytomator configuration and deployment

[overheadhunter]

@ryan

I assume that unicode is fully supported. Would this be a fair assumption?

In passwords, yes. In filenames, theoretically yes but in practise problems seem to occur depending on the setup.

@ryan

As to the availability of metadata, is the only metadata that is exposed the following?

• access, modification, and creation timestamp of files and folders,
• number of files and folders in a vault and in the folders, and
• size of the stored files.

Can this (metadata) be restricted and/or removed?

Correct. You can not “remove” this metadata. Cryptomator is made for the cloud and the cloud sync tools need those timestamps in order to know what to sync. If you want to encrypt stuff for local use, rather use Veracrypt or similar tools, that will hide those metadata.

@ryan

I am assuming that there is no limit to the size of the vault regardless if it’s a local disk or an external disk. Would this be correct?

See this post.

@ryan

What is the risk of corruption and is there the option to validate file integrity e.g. checksum?

If any bit of a file flips, the file is can no longer be decrypted (but it won’t affect other files in the vault). There are checksums in various places (and they are required to prevent accidental decryption of tampered ciphertexts - which would allow some attacks). However, it is possible to recover the file as a whole or at least parts of the file depending on the position of the damaged byte. For the exact probabilities, see this post.