Provided by: ecryptfs-utils_38-2_i386
eCryptfs - an enterprise-class cryptographic filesystem for linux
mount -t ecryptfs [SRC DIR] [DST DIR] -o [OPTIONS]
eCryptfs is a POSIX-compliant enterprise-class stacked cryptographic
filesystem for Linux. It is derived from Erez Zadok’s Cryptfs,
implemented through the FiST framework for generating stacked
filesystems. eCryptfs extends Cryptfs to provide advanced key
management and policy features. eCryptfs stores cryptographic metadata
in the header of each file written, so that encrypted files can be
copied between hosts; the file will be decryptable with the proper key,
and there is no need to keep track of any additional information aside
from what is already in the encrypted file itself. Think of eCryptfs as
a sort of "gnupgfs."
Specify the type of key to be used when mounting eCryptfs.
Specify the symmetric cipher to be used on a per file basis
Specify the keysize to be used with the selected cipher. If
the cipher only has one keysize the keysize does not need to
Allows for non-eCryptfs files to be read and written from
within an eCryptfs mount. This option is turned off by
Do not check the mount key signature against the values in
the user’s ~/.ecryptfs/sig-cache.txt file. This is useful for
such things as non-interactive setup scripts, so that the
mount helper does not stop and prompt the user in the event
that the key sig is not in the cache.
This option, when set, will have eCryptfs return the
encrypted versions of the lower files, rather than decrypt
encrypted files and return the decrypted data from the lower
files. This options is useful for such things as backup
Store the metadata in the extended attribute of the lower
files rather than the header region of the lower files.
Set to ’1’ in order to get verbose output from the kernel
module. As a word of caution, this will cause secret values
to be written in the clear to the system log, so this options
should only be used for debugging purposes.
The actual password is password. Since the password is
visible to utilities (like ’ps’ under Unix) this form should
only be used where security is not important.
The password should be specified in a file with
passwd=(passphrase). It is highly reccomended that the file
be stored on a secure medium such as a personal usb key.
The password is specified through the specified file
passstdin The user types their passphrase in through stdin.
The salt should be specified as a 16 digit hex value.
The filename should be the filename of a file containing an
RSA SSL key.
Do not run eCryptfs in higher verbosity levels unless you are doing so
for the sole purpose of development, since secret values will be
written out to the system log in that case.
Please send bug reports to the lead developer, an eCryptfs mailing list
hosted from SourceForge, or to the SourceForge bug tracker for the
eCryptfs project. For kernel bugs, please follow the procedure detailed
in Documentation/oops-tracing.txt to help us figure out what is