As reported in cryptomator/cryptomator#1617, a crypto file system with a configured maximum file name length that is not equal to 220 leads to a gap where:
file names are too long to be accepted
and at the same time are too short to be shortened
Shortening must therefore be applied as soon as a c9r file name hits the configured threshold.
To ensure deterministic file name encryption, we must make sure to use the file name limit from the shared vault.cryptomator file (see #95) instead of application-specific settings.
As reported in cryptomator/cryptomator#1617, a crypto file system with a configured maximum file name length that is not equal to 220 leads to a gap where:
Shortening must therefore be applied as soon as a c9r file name hits the configured threshold.
To ensure deterministic file name encryption, we must make sure to use the file name limit from the shared
vault.cryptomatorfile (see #95) instead of application-specific settings.