Max file path length question (REWORDED VERSION)

[Michael]

Hi.

@dHFH84H33

What is the max total path length that cryptomator creates when shortening file names/paths?

Based on this information about the security architecture
dirPath := vaultRoot + '/d/' + substr(dirIdHash, 0, 2) + '/' + substr(dirIdHash, 2, 30)
Means: within the folder “d” of your vault, the next level are 2-digits folders, and the next are 30-digits folders.
Please note: this is only for the file path, not for the file names.

Please have a look at this description of name shortening
Based on this, cryptomator checks if the “encrypted” file name (cyphertextName) has more than 129 digits. If yes, a SHA1 Hash is generated from this. The output should not exceed 40-digits .
So, if you have loooooong folder/filenames, they will end up in something like this:

[Volume]:\your\path\to\the\vault \d\CD\S3B6KAWBFDOL2ZCIYWQKQXLK5RPE6V\DDHN3YAO26LBMJ6KMRAWK3TXM4QKVDZDXXXXXXXX.lng
the bold marked part is 81 digits. The other part of the path obviously depends on your setup.

@dHFH84H33

Also please confirm that decrypted vaults viewed in windows explorer have their own 260 (or 247?) character limit (due to explorer’s incompatibility with long paths).

It depends on the volume type you are using. (WebDAV or Dokany).
I made some testing with Windows 1809 in April. Here are my results:

Files invisible in long path names if WebDAV but not Dokany

I played around for some reproduction attempts. (on windows 10 pro 1809) Here are some more information, maybe that helps also: With webdav it turns out that windows is complaining at the moment when the path (only folders) length is 240. A folder structure with 240 digits will not allow to create any files, or copy of anything to a local place. (you have to delete 2 digits to copy the path to a local drive) F:\kjsafnlakjsdflaksjfhlaskjdfhlaksjdfhlakjsdf\0238947023984701298437018293470912834…