From: "Matthew J. Fanto" <mattf@mattjf.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The Ext3sj Filesystem
Date: Wed, 30 Oct 2002 16:33:16 -0500 [thread overview]
Message-ID: <200210301633.16910.mattf@mattjf.com> (raw)
In-Reply-To: <20021030200020.GV28982@clusterfs.com>
On Wednesday 30 October 2002 03:00 pm, Andreas Dilger wrote:
> 1) having so many encryption algorithms is a huge pain in the ass, and
> it will never be accepted into the kernel like that. Pick some
> "good" encryption algorithms (like those that will be supported as
> part of IPSec and/or the encrypted loop devices: 3DES, AES, RC5 or
> whatever) and then there can be some re-use with other parts of the
> kernel.
I don't believe having so many algorithms is such a pain. It gives users more
choices. I've spoke to people who will not trust AES, 3DES, SHA, and even
the AES finalists because they believe NIST/NSA only picked weak algorithms.
Obviously there will be a default algorithm (probably AES and SHA1), so I
don't think having more algorithms will cause users problems. Only problem I
see is maintaining all of them.
-Matthew J. Fanto
next prev parent reply other threads:[~2002-10-30 21:27 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 [this message]
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
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=200210301633.16910.mattf@mattjf.com \
--to=mattf@mattjf.com \
--cc=adilger@clusterfs.com \
--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