Add hint that Cryptomator is case-sensitive

[jeffrson]

trafficstars

Description

When files on a cryptomator drive (via Dokany on an internal NTFS drive) are accessed through a name with differing case representation they cannot be found.

System Setup

• Operating system and version: Windows 10
• Cryptomator version: 1.5.3
• Drive: [Dokany/FUSE/WebDAV] Dokany

Steps to Reproduce

I tried NodeJS, but this shouldn't matter at all:

> let fs=require("fs")
> fs.writeFileSync("test.dat", "test")
> fs.readFileSync("test.dat")
<Buffer 74 65 73 74>
> fs.readFileSync("Test.dat")
Uncaught Error: ENOENT: no such file or directory, open 'Test.dat'
    at Object.openSync (fs.js:461:3)
    at Object.readFileSync (fs.js:364:35) {
  errno: -4058,
  syscall: 'open',
  code: 'ENOENT',
  path: 'Test.dat'
}

Expected Behavior

Well, files should be found and opened without error.

Actual Behavior

There's an "ENOENT" error.

Reproducibility

Always

[overheadhunter]

Cryptomator is case-sensitive. This is inevitable due to deterministic filename encryption (see explanation in cryptomator/cryptomator#622).

There is the possibility to add a case-insensitive mode, which will take O(n*m) instead of O(1) for every file operation that needs to know the name (with n being the number of items in a directory for each element in a path with m elements). This is less than desirable.

[jeffrson]

Since this is quite unexpected in Windows I see a need for documenting this emphasized. It clearly limits straight use of applications on Cryptomator drives.

I really had looked for this information in the community and documentation sites, especially FAQ.