From d530fbd400c88fa54c856d958963d77669ac9cf2 Mon Sep 17 00:00:00 2001
From: Jakob Unterwurzacher
Date: Mon, 1 Nov 2021 14:44:32 +0100
Subject: 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
---
 Documentation/MANPAGE.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

(limited to 'Documentation')

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`.
-- 
cgit v1.2.3