public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Wourms <nwourms@netscape.net>
To: linux-kernel@vger.kernel.org
Subject: Re: The Ext3sj Filesystem
Date: Thu, 31 Oct 2002 11:36:36 -0500	[thread overview]
Message-ID: <aprm29$flg$2@main.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.44L.0210301826410.1697-100000@imladris.surriel.com

Rik van Riel wrote:

> On Wed, 30 Oct 2002, Matthew J. Fanto wrote:
> 
>> I am annoucing the development of the ext3sj filesystem. Ext3sj is a new
>> encrypted filesystem based off ext3. Ext3sj is an improvement over the
>> current loopback solution because we do not in fact require a loopback
>> device.  [snip]  Instead, every file is encrypted seperately
> 
> Very nice, for exactly the reasons you outlined ;)
> 
>> Currently, ext3sj supports the following algorithms: AES, 3DES, Twofish,
>> Serpent, RC6, RC5, RC2, Blowfish, CAST-256, XTea, Safer+, SHA1, SHA256,
>> SHA384, SHA512, MD5, with more to come.  If anyone has any comments,
> 
> How about using the algorithms that are already in the kernel
> via the crypto API so all of the kernel can share the same
> crypto algorithms ?

I agree, as this seems like the logical approach.  However, why not just add 
the missing algorithms in the list above to the CryptoAPI while your at it?  
That way, we really give users a choice over which algorithm they prefer to 
use, but also maintaining a centralized API for them.

Cheers,
Nicholas



  reply	other threads:[~2002-10-31 16:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 19:34 The Ext3sj Filesystem Matthew J. Fanto
2002-10-30 20:00 ` Andreas Dilger
2002-10-30 21:33   ` Matthew J. Fanto
2002-10-31 16:21     ` Henning P. Schmiedehausen
2002-11-01  1:32   ` Bill Davidsen
2002-10-30 20:28 ` Rik van Riel
2002-10-31 16:36   ` Nicholas Wourms [this message]
2002-10-30 20:56 ` Lars Marowsky-Bree
2002-10-30 21:20   ` Matthew J. Fanto
2002-10-30 21:34 ` Bill Davidsen
2002-10-30 21:40   ` Matthew J. Fanto
2002-11-01  4:41 ` Theodore Ts'o
2002-11-01  5:14   ` Matthew J. Fanto

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='aprm29$flg$2@main.gmane.org' \
    --to=nwourms@netscape.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