From owner-freebsd-security Tue Oct 14 06:55:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA17775 for security-outgoing; Tue, 14 Oct 1997 06:55:33 -0700 (PDT) (envelope-from owner-freebsd-security) Received: from silver.sms.fi (silver.sms.fi [194.111.122.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA17757 for ; Tue, 14 Oct 1997 06:55:27 -0700 (PDT) (envelope-from pete@silver.sms.fi) Received: (from pete@localhost) by silver.sms.fi (8.8.7/8.7.3) id QAA21928; Tue, 14 Oct 1997 16:54:26 +0300 (EEST) Date: Tue, 14 Oct 1997 16:54:26 +0300 (EEST) Message-Id: <199710141354.QAA21928@silver.sms.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Petri Helenius To: Antal Rutz Cc: Ollivier Robert , freebsd-security@FreeBSD.ORG Subject: Re: IPv6 sources w/out export restriction In-Reply-To: References: <19970924075951.46946@keltia.freenix.fr> X-Mailer: VM 6.22 under 19.15p7 XEmacs Lucid Sender: owner-freebsd-security@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Antal Rutz writes: > On Wed, 24 Sep 1997, Ollivier Robert wrote: > > > > I'll try to see how much work is it to integrate it into CURRENT. > > -- > Unfortunately they work with whole replacement files not with diffs. > It even can't be compiled under 2.2-stable... > This is why the code should be checked into CURRENT as my impression is that although it undergoes ongoing development, it's still very non-distruptive to non-ipv6 stuff so it would not hurt to be there. Pete