Documentation, filename max length

This commit is contained in:
Ben RUBSON 2018-04-07 14:16:23 +02:00 committed by GitHub
parent 9ad4a7b89a
commit 0fb264d531
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -373,8 +373,8 @@ inherited by B<EncFS> (or possibly be further limited).
One such limitation is filename length. If your underlying filesystem limits One such limitation is filename length. If your underlying filesystem limits
you to N characters in a filename, then B<EncFS> will limit you to approximately you to N characters in a filename, then B<EncFS> will limit you to approximately
3*(N-2)/4. For example if the host filesystem limits to 256 characters, then 3*(N-2)/4. For example if the host filesystem limits to 255 characters, then
B<EncFS> will be limited to 190 character filenames. This is because encrypted B<EncFS> will be limited to 189 character filenames. This is because encrypted
filenames are always longer than plaintext filenames. filenames are always longer than plaintext filenames.
=head1 FILESYSTEM OPTIONS =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 However stream cipher mode may be useful if you want shorter encrypted
filenames for some reason. 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. Prior to version 1.1, only stream encoding was supported.
=item I<Filename Initialization Vector Chaining> =item I<Filename Initialization Vector Chaining>