Yes, but i’d advise against it, because it is not a stable configuration. We struggled a lot with this problem in the past and have now a plan how to solve it, but we are only at the beginning of its implementation.
If you really, really want to, you can perform the following steps. Note, those are written for the upcoming 1.6.0 version of Cryptomator (you can download the beta of it here).
Read the instructions completely before you continue
- Perform the calculations described in Error during updating vault (Cryptomator 1.5.3) - #7 by infeo
- With the resulting value
x, compute the valuey = ((x - 4) / 4 ) * 3 - 16(where an integer division is used and you need to apply the division before the multiplication!) - Create a new vault in the desired storage location (i.e. with name
VAULT), unlock it once and lock it again - Open the log directory over the general preferences
- Quit Cryptomator app
- Open the file
settings.jsonthe log directory with a texteditor - Look for the entry
"displayName": "VAULT", - Replace the value behind the next maxCleartextFilenameLength with your calculated
y(do not delete the comma!) - Save your changes
- Test the setting by starting Cryptomator, unlock the configured vault and try to place a file with more (ASCII) characters than
y→ it should not work - Sync this vault to the cloud
- On every other desktop system, where you access the vault:
i. Add the vault to Cryptomator
ii. Perform steps 5.-10.
Since this setting always only made locally, you have to set it up on every system. Please note that the mobile apps do not allow restricting the filename length. Here you need to be … yeah, well… just careful.^^