extern/encfs
1
0
Fork 0
mirror of https://github.com/vgough/encfs.git synced 2025-04-22 10:19:05 +02:00
Code Issues Packages Projects Releases Wiki Activity

doc: encfs spelling and grammar corrections

Browse Source 
Conflicts:
	encfs/encfs.pod
This commit is contained in:
Sam Gleske 2014-07-25 00:00:17 -04:00 committed by Valient Gough
parent 9d5730e808
commit 8889e5ea5b
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
encfs/encfs.pod
View File

@ -283,8 +283,8 @@ to decode filenames if desired.
B<EncFS> is not a true filesystem. It does not deal with any of the actual B<EncFS> is not a true filesystem. It does not deal with any of the actual
storage or maintenance of files. It simply translates requests (encrypting or storage or maintenance of files. It simply translates requests (encrypting or
decrypting as necessary) and passes the requests through to the underlying decrypting as necessary) and passes the requests through to the underlying
host filesystem. Therefor any limitations of the host filesystem will likely host filesystem. Therefore any limitations of the host filesystem will be
be inherited by B<EncFS> (or possibly be further limited). inherited by B<EncFS> (or possibly be further limited).
One such limitation is filename length. If your underlying filesystem limits One such limitation is filename length. If your underlying filesystem limits
you to N characters in a filename, then B<EncFS> will limit you to approximately you to N characters in a filename, then B<EncFS> will limit you to approximately
@ -341,7 +341,7 @@ function. The number of iterations in the keying function is selected based on
wall clock time to generate the key. In standard mode, a target time of 0.5 wall clock time to generate the key. In standard mode, a target time of 0.5
seconds is used, and in paranoia mode a target of 3.0 seconds is used. seconds is used, and in paranoia mode a target of 3.0 seconds is used.
On a 1.6Ghz AMD 64 system, it rougly 64k iterations of the key derivation On a 1.6Ghz AMD 64 system, roughly 64k iterations of the key derivation
function can be handled in half a second. The exact number of iterations to function can be handled in half a second. The exact number of iterations to
use is stored in the configuration file, as it is needed to remount the use is stored in the configuration file, as it is needed to remount the
filesystem. filesystem.