From 0fb264d531acd59e7de26068f3dfdb4e42830b17 Mon Sep 17 00:00:00 2001 From: Ben RUBSON Date: Sat, 7 Apr 2018 14:16:23 +0200 Subject: [PATCH] Documentation, filename max length --- encfs/encfs.pod | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/encfs/encfs.pod b/encfs/encfs.pod index 51732814..177f69ab 100644 --- a/encfs/encfs.pod +++ b/encfs/encfs.pod @@ -373,8 +373,8 @@ inherited by B (or possibly be further limited). One such limitation is filename length. If your underlying filesystem limits you to N characters in a filename, then B will limit you to approximately -3*(N-2)/4. For example if the host filesystem limits to 256 characters, then -B will be limited to 190 character filenames. This is because encrypted +3*(N-2)/4. For example if the host filesystem limits to 255 characters, then +B will be limited to 189 character filenames. This is because encrypted filenames are always longer than plaintext filenames. =head1 FILESYSTEM OPTIONS @@ -488,6 +488,11 @@ on by default, as it takes a similar amount of time to using the stream cipher. However stream cipher mode may be useful if you want shorter encrypted filenames for some reason. +Based on an underlying filesystem supporting a maximum of 255 characters in +filenames, here is the maximum possible filename length depending on the choosen +encoding scheme : stream (189), block (176), block32 (143). Note that we should +rather talk about bytes, when filenames contain special (multi-bytes) characters. + Prior to version 1.1, only stream encoding was supported. =item I