Date: Mon, 23 Jun 1997 12:38:55 +0300 (EEST) From: Narvi <narvi@haldjas.folklore.ee> To: itojun@itojun.org Cc: freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: ipsec code made in Japan Message-ID: <Pine.BSF.3.96.970623123403.17008A-100000@haldjas.folklore.ee> In-Reply-To: <12196.867054658@itojun.csl.sony.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
Cool! I will try it. As for merging, it could probably have a branch on the international crypto sources? Of course, provided it is accepted. There is no love, no good, no happiness and no future - all these are just illusions. On Mon, 23 Jun 1997 itojun@itojun.org wrote: > I've made a IPv4 IPsec patch to 2.2.1-RELEASE, in: > ftp://ftp.csl.sony.co.jp/pub/itojun/ipsec/ > (should be easily applied to 222-RELEASE too) > Please read the following document with care BEFORE downloading it. > ftp://ftp.csl.sony.co.jp/pub/itojun/ipsec/README > > Cryptographic code is implemented outside of US, so there would > be no export control problem for most people. (except for > countries where import of crypto code is illegal, or use of crypto > code is illegal) > > It is still in infancy, and will be updated regularly. > Please visit the above directory regulary, if you would like to > do a beta-test. > > Currently, there's no dynamic key management daemon available. > (I plan to port Pluto implementation) > If you would like to find WAN testing partner, email me. > There are several people running this kernel, so let us manuall > setup keys manually. > > > Question: How should I release this kind of code in the future? > What is the best way for us all? Apparently I can't try to merge > it into FreeBSD source tree in ftp.freebsd.org. > > Jun-ichiro itojun Itoh > itojun@itojun.org >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970623123403.17008A-100000>