Subject: Re: what to put into cryptosrc-intl tree
To: None <firstname.lastname@example.org>
From: Michael C. Richardson <email@example.com>
Date: 06/23/1999 13:32:52
>>>>> "Perry" == Perry E Metzger <firstname.lastname@example.org> writes:
Perry> "Michael C. Richardson" <email@example.com> writes:
>> 2. we import KAME IPsec. It appears that there is movement towards
>> using KAME as a route toward unified ipv6, and there is desire to do
>> this for 1.5.
Perry> I suggest you let Itojun do the work on this. He's already outside
Perry> the U.S.
I do intend to do that :-)
"We" includes Itojun.
Perry> The only parts that need to be put into cryptosrc-intl will be the
Perry> ESP stuff, since the rest is exportable.
>> 4. kerberos IV (eBones)
Perry> I oppose this. No new code using DES. DES is not good enough for
Perry> our source tree.
Okay, noted. Isn't there a way to use 3DES with IV?
:!mcr!: | Cow#1: Are you worried about getting Mad Cow Disease?
Michael Richardson | Cow#2: No. I'm a duck.
Home: firstname.lastname@example.org. PGP key available.