file_encryption » Revisions »

Differences

This shows you the differences between the selected revisions of the page.

file_encryption 2019-03-27		file_encryption 2019-11-23 (current)
	Line 22:		Line 22:
	* When creating a new folder, its //name// is //encrypted// by default (can be changed in default transfer settings).		* When creating a new folder, its //name// is //encrypted// by default (can be changed in default transfer settings).

-	You can identify encrypted files and folders using a lock overlay icon.	+	You can identify encrypted files and folders using a [[ui_file_panel#special_files\|lock overlay icon]].

	===== [[requirements]] Requirements on Server File System =====		===== [[requirements]] Requirements on Server File System =====

-	Encryption of file names uses Base64 encoding. To preserve file names encoded in Base64 encoding, the target file system should be case-sensitive (Linux servers use case-sensitive file systems) or at least case-preserving (with a small risk of collision - Windows NTFS is case-preserving).	+	Encryption of file names uses Base64 encoding. To preserve file names encoded in Base64 encoding, the target file system should be case-sensitive (Linux servers use case-sensitive file systems) or at least case-preserving (with a small risk of collision -- Windows NTFS is case-preserving).

	The file system also needs to support reasonably long file names. Base64 encoding adds a 33% overhead to a filename length. Additionally, an encoded salt and the ''.aesctr.enc'' extension add another approximately 33 characters.		The file system also needs to support reasonably long file names. Base64 encoding adds a 33% overhead to a filename length. Additionally, an encoded salt and the ''.aesctr.enc'' extension add another approximately 33 characters.