[PATCH 2/12: eCryptfs] Documentation

From: Phillip Hellewell
Date: Fri Nov 18 2005 - 23:15:52 EST

This patch provides documentation for using eCryptfs.

Signed-off-by: Phillip Hellewell <phillip@xxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Michael Halcrow <mhalcrow@xxxxxxxxxx>


ecryptfs.txt | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 81 insertions(+)
--- linux-2.6.15-rc1-mm1/Documentation/ecryptfs.txt 1969-12-31 18:00:00.000000000 -0600
+++ linux-2.6.15-rc1-mm1-ecryptfs/Documentation/ecryptfs.txt 2005-11-18 11:46:12.000000000 -0600
@@ -0,0 +1,81 @@
+eCryptfs: A stacked cryptographic filesystem for Linux
+Maintainer: Phillip Hellewell
+Lead developer: Michael A. Halcrow <mhalcrow@xxxxxxxxxx>
+Developers: Michael C. Thompson
+ Kent Yoder
+Current Release Version: 0.1
+This software is currently undergoing development. Make sure to
+maintain a backup copy of any data you write into eCryptfs.
+eCryptfs requires the userspace tools downloadable from the
+SourceForge site:
+Requirements include:
+ - Kernel version 2.6.15-rc1-mm1 or higher
+ - eCryptfs will work with 2.6.14, but you will need the
+ export_user_type.patch applied
+ - David Howells' userspace keyring headers and libraries, obtainable
+ from http://people.redhat.com/~dhowells/keyutils/
+ - (You will need to apply the keyutil_h_fix.diff patch to version 0.3)
+ - GnuPG Made Easy (GPGME)
+ - Building the kernel with:
+ - Cryptographic API
+ - Blowfish cipher
+ - Key retention support
+ - Filesystems->Miscellaneous filesystems->eCryptfs
+If you are installing from the patch set:
+1) Apply export_user_type.patch to the kernel if you are running
+ kernel version 2.6.14
+2) Apply all patches in the patches/ directory to the kernel
+Once eCryptfs is already in the kernel:
+3) Select build options (see Requirements) and build kernel
+4) Apply keyutil_h_fix.diff to the keyutils if you are running version
+ 0.3
+5) Run make and make install from the request-key/ directory.
+Create a new directory into which eCryptfs will write its encrypted
+files (i.e., /root/crypt). Then, create the mount point directory
+(i.e., /mnt/crypt). Now it's time to mount eCryptfs:
+mount -t ecryptfs /root/crypt /mnt/crypt
+You should be prompted for a passphrase and a salt (the salt may be
+Try writing a new file:
+echo "Hello, World" > /mnt/crypt/hello.txt
+The operation will complete. Notice that there is a new file in
+/root/crypt that is 3 pages (12288 bytes) in size. This is the
+encrypted underlying file for what you just wrote. To test reading,
+from start to finish, you need to clear the user session keyring:
+keyctl clear @u
+Then umount /mnt/crypt and mount again per the instructions given
+cat /mnt/crypt/hello.txt
+eCryptfs should only be mounted on (1) empty directories or (2)
+directories containing files only created by eCryptfs. If you mount a
+directory that has pre-existing files not created by eCryptfs, then
+behavior is undefined.
+Mike Halcrow
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/