All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Halcrow <mhalcrow@us.ibm.com>
To: akpm@osdl.org
Cc: mhalcrow@us.ibm.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] eCryptfs: Public key support
Date: Thu, 24 Aug 2006 13:17:22 -0500	[thread overview]
Message-ID: <20060824181722.GA17658@us.ibm.com> (raw)

This first two patches in this patch set introduce public key support
into the eCryptfs kernel module shipping in 2.6.18-rc4-mm2. The last
two patches clean up the flag manipulation code and resolve a compiler
warning.

The userspace code that supports the public key mode of operation is
available in the file labeled
``ecryptfs-util-2.6.18-rc4-mm2++.tar.bz2'':

http://sourceforge.net/project/showfiles.php?group_id=133988&package_id=149785

Notice that the version numbers are incremented; the userspace tools
must be upgraded when running with this patch set. Follow the file
migration instructions in the NOTES section of
Documentation/ecryptfs.txt.

On open of an existing encrypted file, eCryptfs reads the public key
packet from the file header and sends a decrypt request packet via
netlink to the user's daemon. If the file is being created, eCryptfs
sends an encrypt request. The daemon processes the request through the
pluggable PKI module associated with the public key involved in the
request.

For those who wish to try out eCryptfs on older kernels, we are also
keeping backports of eCryptfs in packages under the ``ecryptfs-full''
release section:

http://sourceforge.net/project/showfiles.php?group_id=133988&package_id=198555

Mike

             reply	other threads:[~2006-08-24 18:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24 18:17 Michael Halcrow [this message]
2006-08-24 18:18 ` [PATCH 1/4] eCryptfs: Netlink functions for public key Michael Halcrow
2006-08-25  3:54   ` Andrew Morton
2006-08-25 19:18     ` Michael Halcrow
2006-08-28 20:02       ` Andrew Morton
2006-08-24 18:19 ` [PATCH 2/4] eCryptfs: Public key header packets Michael Halcrow
2006-08-24 18:20 ` [PATCH 3/4] eCryptfs: Open-code flag manipulation Michael Halcrow
2006-08-24 18:20 ` [PATCH 4/4] eCryptfs: ino_t to u64 for filldir Michael Halcrow
2006-08-25 21:42 ` [PATCH 3/4] eCryptfs: Open-code flag manipulation David Howells
2006-08-25 21:42 ` [PATCH 4/4] eCryptfs: ino_t to u64 for filldir David Howells
2006-08-25 21:51 ` David Howells
2006-08-25 22:16   ` Michael Halcrow
2006-08-25 22:59   ` David Howells
2006-08-30 21:12     ` Michael Halcrow
2006-08-31 10:30     ` David Howells
2006-09-04 22:54       ` Michael Halcrow
2006-09-06  9:44       ` David Howells
2006-09-06 23:20         ` Michael Halcrow
2006-09-07 10:28         ` David Howells

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=20060824181722.GA17658@us.ibm.com \
    --to=mhalcrow@us.ibm.com \
    --cc=akpm@osdl.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.