diff options
| author | Jakob Unterwurzacher | 2017-10-04 23:40:58 +0200 |
|---|---|---|
| committer | Jakob Unterwurzacher | 2017-10-04 23:40:58 +0200 |
| commit | 954ac7152003687d0431514ca4d8644d301be998 (patch) | |
| tree | f7b7343b60ecb8fd23a21a9681f8ddfb238944c6 /docs | |
| parent | 4a04e35b212655f6ffbea14d6da9040cca22f615 (diff) | |
Actual filename limit is 175 due to padding
See https://github.com/rfjakob/gocryptfs/commit/4da245c69d7994efec75e1deaef56a03020d39db
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/forward_mode_crypto.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/forward_mode_crypto.md b/docs/forward_mode_crypto.md index 423efc4..5515eb0 100644 --- a/docs/forward_mode_crypto.md +++ b/docs/forward_mode_crypto.md @@ -67,15 +67,15 @@ encryption.  -The Base64 encoding limits the usable filename length to 176 characters. +Padding and base64-encoding limit the usable filename length to 175 characters. Filenames that are longer than that (longer than 255 characters in Base64-encoded form) use long file name handling, introduced in gocryptfs v0.9. Long File Name Handling ----------------------- -If the Base64-encoded encrypted name is longer than 255 characters, -it cannot be used as the file name on disk, as Linux filesystems +If the base64-encoded encrypted name is longer than 255 characters, +it cannot be used as the file name on disk, as common Linux filesystems do not allow names longer than that. Instead, the encrypted name is hashed, and the file content is stored in @@ -94,7 +94,7 @@ Example directory listing containing an 1 MiB encrypted file with a long name: ``` This method for storing long file names has zero performance impact -for filenames that are <= 176 characters, incurs no extra disk accesses +for filenames that are <= 175 characters, incurs no extra disk accesses for opening a file with a long name, and just one extra file read for each long-name file on readdir(1). |