summaryrefslogtreecommitdiff
path: root/user/encfs/length.patch
blob: be3f373c32b2f6dbf7ab26c466966f8e67eb4b69 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
From dafeb556d27076b0c6fa23e44e523bdd84598838 Mon Sep 17 00:00:00 2001
From: Ben RUBSON <ben.rubson@gmail.com>
Date: Sun, 9 Dec 2018 11:28:42 +0100
Subject: [PATCH] Correct block filename max length (#540)

---
 encfs/encfs.pod | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/encfs/encfs.pod b/encfs/encfs.pod
index 6cb5b8f5..d3831296 100644
--- a/encfs/encfs.pod
+++ b/encfs/encfs.pod
@@ -490,7 +490,7 @@ 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
+encoding scheme : stream (189), block (175), 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.