From: Kyle McMartin <kyle@debian.org>
To: "David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] IPsec: add support for Twofish and Serpent
Date: Fri, 15 Aug 2003 13:42:43 -0400 [thread overview]
Message-ID: <20030815174243.GC3119@imladris.debian.net> (raw)
In-Reply-To: <20030814191259.435945cf.davem@redhat.com>
On Thu, Aug 14, 2003 at 07:12:59PM -0700, David S. Miller wrote:
> I totally disagree, choice is everything.
>
> That's why we allow NULL crypto algorithms. Not doing
> so turns this into a political thing, which I decidedly
> do not want our IPSEC implementation to be all about.
>
> And therefore I will add the patch.
>
Thank you, David. I completely agree with allowing users to choose
which algorithms they wish to deploy.
> When using pfkeyv2 sockets, yes you have to assign a number and then
> the APP has to be aware of it. This just shows how bogus it is to use
> fixed numbers instead of strings to select crypto algorithms.
>
Again, I agree. Especially given the limitations of using the
private ESP id space, since there is no new RFC delegating
additions yet.
Regards,
--
Kyle McMartin <kyle@debian.org>
1024D/191FCD8A - 331A 9468 C04D 3A76 5C56 BA68 7EB7 92DF 191F CD8A
2048R/F515317D - 68 A9 0D 28 1B DF 8D 42 0F CC AF 98 A8 D5 A4 04
next prev parent reply other threads:[~2003-08-15 17:42 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
2003-08-14 20:25 ` Pekka Savola
2003-08-15 2:12 ` David S. Miller
2003-08-15 17:42 ` Kyle McMartin [this message]
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=20030815174243.GC3119@imladris.debian.net \
--to=kyle@debian.org \
--cc=davem@redhat.com \
--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).