public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Hellewell <phillip@hellewell.homeip.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] eCryptfs: eCryptfs kernel module
Date: Wed, 1 Jun 2005 23:47:40 -0600	[thread overview]
Message-ID: <20050602054740.GA4514@sshock.rn.byu.edu> (raw)

This is the first in a series of 3 patches for the eCryptfs kernel
module.

eCryptfs is a cryptographic filesystem that stacks on top of other
filesystems.  A very early version of it was presented last year at
OLS, and the current version will be presented again at this year's
OLS.  It is currently in an EXPERIMENTAL and BROKEN state (i.e., it
will build and run, but there is at least one memory leak that causes
a problem when a several dozen file open/read/write operations are
performed).  It requires userspace components to run, which can be
obtained via CVS from the eCryptfs project site:

http://sourceforge.net/projects/ecryptfs

The README file from CVS explains how to get it up and running with
both passphrase and public key (PKI) operation modes.

While eCryptfs is functional, there is a significant amount of work
yet to be done; a perusal of the source will reveal that there is a
lot of low-hanging fruit/trivial fixes (David Howells: we promise that
using your keyring correctly is near the top of the list, right after
we get these memory leaks resolved).  It derives from cryptfs, which
is a cryptographic filesystem instantiated by Erez Zadok's stackable
filesystem framework, FiST.  We are aware that there are some extant
bugs in the version of cryptfs that we built off of; as those are made
known, we will be applying fixes.  In the meantime, we would like the
eCryptfs kernel module to be merged into the mainline kernel.  We are
open to suggestions and commentary on the general design of the
filesystem, and bugfixes are always welcome too.

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

This first patch is somewhat large (45K), so here is a link:

http://ecryptfs.sourceforge.net/patches/patch-2.6.12-rc4-mm2-ecryptfs-1_of_3.diff.gz

-- 
Phillip Hellewell <phillip AT hellewell.homeip.net>

             reply	other threads:[~2005-06-02  5:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02  5:47 Phillip Hellewell [this message]
2005-06-02  7:33 ` [PATCH 1/3] eCryptfs: eCryptfs kernel module Greg KH
2005-06-02  7:33   ` James Morris
2005-06-02 12:32     ` Michael Halcrow
2005-06-02 14:51       ` Greg KH
2005-06-02 12:28   ` Michael Halcrow
2005-06-02 14:52     ` Greg KH
2005-06-02 16:33     ` James Morris

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=20050602054740.GA4514@sshock.rn.byu.edu \
    --to=phillip@hellewell.homeip.net \
    --cc=linux-kernel@vger.kernel.org \
    /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