From owner-freebsd-hackers  Mon Aug 30 23:58:24 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by hub.freebsd.org (Postfix) with ESMTP
	id 530881535F; Mon, 30 Aug 1999 23:58:09 -0700 (PDT)
	(envelope-from itojun@itojun.org)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id PAA18845;
	Tue, 31 Aug 1999 15:57:53 +0900 (JST)
To: Mark Murray <mark@grondar.za>
Cc: core@FreeBSD.ORG, hackers@FreeBSD.ORG
In-reply-to: mark's message of Tue, 31 Aug 1999 08:42:22 +0200.
      <199908310642.IAA33895@gratis.grondar.za> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: KAME IPv6 and freebsd 
From: itojun@iijlab.net
Date: Tue, 31 Aug 1999 15:57:53 +0900
Message-ID: <18843.936082673@coconut.itojun.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>> 	KAME team really needs your suggestions on how to integrate crypto
>> 	part.  In case of NetBSD/KAME integration, we did like this:
>> 	- place IPsec core part and AH part into cvs.netbsd.org (in US)
>> 	- place ESP part and crypto algorithms (DES, Blowfish and whatever
>> 	  in cvs.fi.netbsd.org (in finland)
>> 	We need some tricky symbolic link, or makefile/config hack for this
>> 	separated repository (NetBSD has makefile and config hack).
>FreeBSD has the src/crypto directory for this purpose. It works in
>exactly the same way as src/contrib, but contains code that may
>get Americans into trouble if they export it, so I maintain a copy
>in South Africa (on internat.freebsd.org).
>I'll be very happy to work with you on this one.

	Does it make sense to make src/crypto/sys for kernel code?
	(for IPsec we need crypto code *in kernel*).

itojun


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message