mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phillip Hellewell <phillip@hellewell.homeip.net>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: phillip@hellewell.homeip.net, mike@halcrow.us,
	mhalcrow@us.ibm.com, mcthomps@us.ibm.com, yoder1@us.ibm.com
Subject: [PATCH 2/12: eCryptfs] Documentation
Date: Wed, 2 Nov 2005 20:43:08 -0700	[thread overview]
Message-ID: <20051103034308.GB3005@sshock.rn.byu.edu> (raw)
In-Reply-To: <20051103033220.GD2772@sshock.rn.byu.edu>

This patch provides documentation for using eCryptfs.

Signed off by: Phillip Hellewell <phillip@hellewell.homeip.net>
Signed off by: Michael Halcrow <mhalcrow@us.ibm.com>
Signed off by: Michael Thompson <mmcthomps@us.ibm.com>
Signed off by: Kent Yoder <yoder1@us.ibm.com>

 ecryptfs.txt |   55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 55 insertions(+)
--- linux-2.6.14-rc5-mm1/Documentation/ecryptfs.txt	1969-12-31 18:00:00.000000000 -0600
+++ linux-2.6.14-rc5-mm1-ecryptfs/Documentation/ecryptfs.txt	2005-11-01 16:47:17.000000000 -0600
@@ -0,0 +1,55 @@
+eCryptfs: A stacked cryptographic filesystem for Linux
+Maintainer: Phillip Hellewell
+Lead developer: Michael A. Halcrow <mhalcrow@us.ibm.com>
+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:
+
+http://sourceforge.net/projects/ecryptfs/
+
+Run make and make install from the request-key/ directory.
+
+
+MOUNT-WIDE PASSPHRASE
+
+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
+blank).
+
+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
+above.
+
+cat /mnt/crypt/hello.txt
+
+
+NOTES
+
+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
+mhalcrow@us.ibm.com

  parent reply	other threads:[~2005-11-03  3:42 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03  3:32 [PATCH 0/12: eCryptfs] eCryptfs version 0.1 Phillip Hellewell
2005-11-03  3:42 ` [PATCH 1/12: eCryptfs] Makefile and Kconfig Phillip Hellewell
2005-11-03 15:21   ` Michael Thompson
2005-11-03 23:05     ` Greg KH
2005-11-04 16:09       ` Michael Thompson
2005-11-04 16:22         ` Anton Altaparmakov
2005-11-04 16:28           ` Michael Thompson
2005-11-04 16:35         ` Greg KH
2005-11-04 17:07           ` Michael Thompson
2005-11-03  3:43 ` Phillip Hellewell [this message]
2005-11-03  3:43 ` [PATCH 3/12: eCryptfs] Makefile Phillip Hellewell
2005-11-03  3:49 ` [PATCH 4/12: eCryptfs] Main module functions Phillip Hellewell
2005-11-03  6:02   ` Greg KH
2005-11-03 15:09     ` Michael Thompson
2005-11-03 15:47       ` Alexey Dobriyan
2005-11-03 15:40         ` Michael Thompson
2005-11-03 21:34     ` Michael Thompson
2005-11-04 23:28     ` [PATCH: eCryptfs] Remove debug wrappers Michael Halcrow
2005-11-03  3:50 ` [PATCH 5/12: eCryptfs] Header declarations Phillip Hellewell
2005-11-03 23:37   ` James Morris
2005-11-03  3:51 ` [PATCH 6/12: eCryptfs] Superblock operations Phillip Hellewell
2005-11-03 23:47   ` James Morris
2005-11-03  3:52 ` [PATCH 7/12: eCryptfs] File operations Phillip Hellewell
2005-11-03 23:49   ` James Morris
2005-11-03  3:53 ` [PATCH 8/12: eCryptfs] Dentry operations Phillip Hellewell
2005-11-03  3:54 ` [PATCH 9/12: eCryptfs] Inode operations Phillip Hellewell
2005-11-03 23:51   ` James Morris
2005-11-04  0:24     ` Andreas Schwab
2005-11-04  6:29       ` James Morris
2005-11-03  3:55 ` [PATCH 10/12: eCryptfs] Mmap operations Phillip Hellewell
2005-11-03  5:32   ` Michael Halcrow
2005-11-07 20:39     ` [PATCH: eCryptfs] Encrypt on writepage() Michael Halcrow
2005-11-03  3:56 ` [PATCH 11/12: eCryptfs] Keystore Phillip Hellewell
2005-11-03 23:59   ` James Morris
2005-11-04  0:08     ` Michael Halcrow
2005-11-04 17:52   ` Timothy R. Chavez
2005-11-03  3:56 ` [PATCH 12/12: eCryptfs] Crypto functions Phillip Hellewell
2005-11-03 22:06   ` Dave Kleikamp
2005-11-03 22:25     ` Michael Thompson
2005-11-03 22:30       ` Dave Kleikamp
2005-11-04  0:08   ` James Morris
2005-11-04  0:14     ` Michael Halcrow
2005-11-19  4:11 [PATCH 0/12: eCryptfs] eCryptfs version 0.1 Phillip Hellewell
2005-11-19  4:16 ` [PATCH 2/12: eCryptfs] Documentation Phillip Hellewell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051103034308.GB3005@sshock.rn.byu.edu \
    --to=phillip@hellewell.homeip.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcthomps@us.ibm.com \
    --cc=mhalcrow@us.ibm.com \
    --cc=mike@halcrow.us \
    --cc=yoder1@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®