summaryrefslogtreecommitdiff
path: root/tests/example_filesystems/v1.3/gocryptfs.longname.QhUr5d9FHerwEs--muUs6_80cy6JRp89c1otLwp92Cs.name
diff options
context:
space:
mode:
authorJakob Unterwurzacher2021-11-01 14:44:32 +0100
committerJakob Unterwurzacher2021-11-01 14:44:32 +0100
commitd530fbd400c88fa54c856d958963d77669ac9cf2 (patch)
treed43ee0ed0ab4738e4fe5a77ceed3222740f3842c /tests/example_filesystems/v1.3/gocryptfs.longname.QhUr5d9FHerwEs--muUs6_80cy6JRp89c1otLwp92Cs.name
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 'tests/example_filesystems/v1.3/gocryptfs.longname.QhUr5d9FHerwEs--muUs6_80cy6JRp89c1otLwp92Cs.name')
0 files changed, 0 insertions, 0 deletions