public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: Encrypted Filesystem
Date: Mon, 26 Jan 2004 16:06:45 -0800	[thread overview]
Message-ID: <20040127000645.GE11879@pegasys.ws> (raw)
In-Reply-To: <OFA97B290B.67DE842E-ON87256E27.0061728C-86256E27.0061BB0E@us.ibm.com>

On Mon, Jan 26, 2004 at 11:46:29AM -0600, Michael A Halcrow wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I have some time this year to work on an encrypted filesystem for
> Linux.  I have surveyed various LUG's, tested and reviewed code for
> currently existing implementations, and have started modifying some
> of them.  I would like to settle on a single approach on which to
> focus my efforts, and I am interested in getting feedback from the
> LKML community as to which approach is the most feasible.
> 
> This is the feature wish-list that I have compiled, based on personal
> experience and feedback I have received from other individuals and
> groups:

This sounds more like transparent (in-kernel?) file encryption 
than an encrypted filesystem.  I think there is value in
having both, or all three if you add encrypted block devices.


-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

  parent reply	other threads:[~2004-01-27  0:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 17:46 Encrypted Filesystem Michael A Halcrow
2004-01-26 19:06 ` Mark Borgerding
2004-01-26 21:04   ` Felipe Alfaro Solana
2004-01-30 17:01     ` Pavel Machek
2004-01-27  0:06 ` jw schultz [this message]
2004-01-27  0:43 ` Adam Sampson
2004-01-27  1:42   ` Andy Isaacson
2004-01-27 22:01   ` Jan Harkes
2004-01-27 22:16     ` Jean-Luc Cooke
2004-01-28 13:50   ` Userspace filesystems (WAS: Encrypted Filesystem) Miklos Szeredi
2004-01-30 17:06     ` Pavel Machek
2004-02-02  9:42       ` Miklos Szeredi
2004-02-02 15:19         ` Pavel Machek
2004-02-02 15:36           ` Nikita Danilov
     [not found] <16405.24299.945548.174085@laputa.namesys.com>
2004-01-26 19:02 ` Encrypted Filesystem Hans Reiser
2004-01-27 18:56   ` Edward Shishkin
2004-01-27 21:25     ` Michael Halcrow
2004-01-27 21:51       ` Hans Reiser
     [not found] <OFA97B290B.67DE842E-ON87256E27.0061728C-86256E27.0061BB0E@us.ibm.com.suse.lists.linux.kernel>
2004-01-27 16:13 ` Andi Kleen
2004-01-27 18:17   ` Jari Ruusu
2004-01-27 18:44     ` Andi Kleen

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=20040127000645.GE11879@pegasys.ws \
    --to=jw@pegasys.ws \
    --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