Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA17581; Mon, 27 Nov 95 21:27:11 EST Received: from pain.lcs.mit.edu by MIT.EDU with SMTP id AA22622; Mon, 27 Nov 95 21:26:10 EST Received: (from daemon@localhost) by pain.lcs.mit.edu (8.6.12/8.6.9) id VAA27066; Mon, 27 Nov 1995 21:06:57 -0500 Received: from jekyll.piermont.com by pain.lcs.mit.edu (8.6.12/8.6.9) with ESMTP id UAA27028 for ; Mon, 27 Nov 1995 20:50:11 -0500 Received: (from perry@localhost) by jekyll.piermont.com (8.6.12/8.6.12) id UAA11407; Mon, 27 Nov 1995 20:49:59 -0500 Date: Mon, 27 Nov 1995 20:49:59 -0500 Message-Id: <199511280149.UAA11407@jekyll.piermont.com> From: "Perry E. Metzger" To: netbsd-developers@netbsd.org Subject: domestic kernel sources? Reply-To: perry@piermont.com X-Reposting-Policy: redistribute only with permission Sender: owner-netbsd-developers@NetBSD.ORG Precedence: first-class X-Loop: netbsd-developers@NetBSD.ORG So I have a problem - I'm porting (its already 4.4lite, so it isn't exactly rocket science) NRL's IPv6 stack to NetBSD. Part of their distribution is an IPSEC implementation, for both v6 and v4. Unfortunately, IPSEC is almost certainly a "munition" under the brain dead definitions followed by the idiots in Washington. We haven't had crypto code in the kernel before. How do we handle it? Its mixed in in odd places -- parts, for instance, of the PF_KEY sockets (used to tell the kernel about keying material) are scattered in other files. I'd like to be able to put this in the main branch at some point so its all an issue... Perry