libgocryptfs/Documentation
Jakob Unterwurzacher d530fbd400 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
2021-11-01 14:44:32 +01:00
..
.gitignore Update gocryptfs-xray manpage, have MANPAGE-render.bash generate both 2019-01-04 20:12:07 +01:00
CLI_ABI.md Assorted spelling fixes. 2018-12-27 15:19:55 +01:00
duplicate-inodes.txt main: add "-sharedstorage" flag 2017-11-12 20:06:13 +01:00
extractloop_plot_csv.png doc: update extractloop results 2019-01-05 12:17:17 +01:00
extractloop.md doc: update extractloop results 2019-01-05 12:17:17 +01:00
file-format.md doc: file-format.md: describe XChaCha20-Poly1305 2021-08-26 08:43:41 +02:00
folders-side-by-side.gif README: Add folders side-by-side animation gif 2018-07-01 15:28:22 +02:00
gocryptfs-logo.png README: use pre-rendered PNG logo 2017-03-25 14:22:07 +01:00
MANPAGE-render.bash shell scripts: fix shellcheck warnings 2021-09-01 10:22:01 +02:00
MANPAGE-STATFS.md Expand statfs man page a little and include in build.bash 2019-09-08 15:50:05 +02:00
MANPAGE-XRAY.md gocryptfs-xray: document -encrypt-paths / -decrypt-paths 2020-05-10 00:14:03 +02:00
MANPAGE.md docs: names longer than 175 bytes (not 176) are stored in longnames 2021-11-01 14:44:32 +01:00
performance-reverse.txt Update reverse benchmarks 2018-08-18 12:25:03 +02:00
performance.txt doc: update performance.txt 2021-06-26 20:57:39 +02:00
SECURITY.md Link to official website; move security document 2015-12-20 18:25:10 +01:00
XFSTESTS.md *: trim trailing whitespace 2021-09-01 10:22:01 +02:00