summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJakob Unterwurzacher2021-11-01 14:44:32 +0100
committerJakob Unterwurzacher2021-11-01 14:44:32 +0100
commitd530fbd400c88fa54c856d958963d77669ac9cf2 (patch)
treed43ee0ed0ab4738e4fe5a77ceed3222740f3842c /Documentation
parent87a6bb370acc3690e89a8b0d5109fcb0dab0a374 (diff)
docs: names longer than 175 bytes (not 176) are stored in longnames
Quoting fusefrontend_reverse/node_helpers.go : // File names are padded to 16-byte multiples, encrypted and // base64-encoded. We can encode at most 176 bytes to stay below the 255 // bytes limit: // * base64(176 bytes) = 235 bytes // * base64(192 bytes) = 256 bytes (over 255!) // But the PKCS#7 padding is at least one byte. This means we can only use // 175 bytes for the file name. Noticed by @bailey27 at https://github.com/rfjakob/gocryptfs/issues/499#issuecomment-955790427
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/MANPAGE.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/Documentation/MANPAGE.md b/Documentation/MANPAGE.md
index b9c72dd..ffed44e 100644
--- a/Documentation/MANPAGE.md
+++ b/Documentation/MANPAGE.md
@@ -318,9 +318,10 @@ the directories. Example:
gocryptfs -ko noexec /tmp/foo /tmp/bar
#### -longnames
-Store names longer than 176 bytes in extra files (default true)
-This flag is useful when recovering old gocryptfs filesystems using
-"-masterkey". It is ignored (stays at the default) otherwise.
+Store names that are longer than 175 bytes in extra files (default true).
+
+This flag is only useful when recovering very old gocryptfs filesystems (gocryptfs v0.8 and earlier)
+using "-masterkey". It is ignored (stays at the default) otherwise.
#### -nodev
See `-dev, -nodev`.