From: Pekka Pietikainen <pp@netppl.fi>
To: Kyle McMartin <kyle@debian.org>
Cc: jmorris@intercode.com.au, netdev@oss.sgi.com, davem@redhat.com
Subject: Re: [PATCH] IPsec: add support for Twofish and Serpent
Date: Thu, 14 Aug 2003 21:08:57 +0300 [thread overview]
Message-ID: <20030814180857.GA4205@netppl.fi> (raw)
In-Reply-To: <20030814164819.GA18948@imladris.debian.net>
On Thu, Aug 14, 2003 at 12:48:19PM -0400, Kyle McMartin wrote:
>
> This patch adds support for the use of twofish and serpent as
> ESP algorithms. The ESP index numbers given are in accordance
> with RFC2407, draft-ietf-ipsec-ciph-aes-cbc-00 (before Rijndael
> was selected), and KAME which assigns 253 to twofishcbc.
> Support for using twofish was requested on linux-kernel, and
> since I noticed serpent was missing too, included that as well.
Hi
Nothing against twofish or serpent per se, but I have this feeling that
supporting every possible crypto algoritm known to man
is not necessarily wise (see eg. Practical Cryptography for the rationale).
There's absolutely no need to add complexity unless there are some technical
arguments for doing so, say compatibility with legacy implementations
which justifies bothering with DES/3DES/MD5 although they're inferior to
AES and SHA1 in just about every aspect.
--
Pekka Pietikainen
next prev parent reply other threads:[~2003-08-14 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 16:48 [PATCH] IPsec: add support for Twofish and Serpent Kyle McMartin
2003-08-14 18:08 ` Pekka Pietikainen [this message]
2003-08-14 20:25 ` Pekka Savola
2003-08-15 2:12 ` David S. Miller
2003-08-15 17:42 ` Kyle McMartin
2003-08-15 17:34 ` Kyle McMartin
2003-08-15 17:38 ` Kyle McMartin
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=20030814180857.GA4205@netppl.fi \
--to=pp@netppl.fi \
--cc=davem@redhat.com \
--cc=jmorris@intercode.com.au \
--cc=kyle@debian.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).