From owner-cvs-all Wed Feb 25 07:03:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29371 for cvs-all-outgoing; Wed, 25 Feb 1998 07:03:20 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29343 for ; Wed, 25 Feb 1998 07:03:12 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id KAA16263; Wed, 25 Feb 1998 10:03:00 -0500 (EST) (envelope-from wollman) Date: Wed, 25 Feb 1998 10:03:00 -0500 (EST) From: Garrett Wollman Message-Id: <199802251503.KAA16263@khavrinen.lcs.mit.edu> To: Jun-ichiro itojun Itoh Cc: cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: src/sys/netkey key.c In-Reply-To: <7197.888390808@coconut.itojun.org> References: <199802250641.WAA02218@freefall.freebsd.org> <7197.888390808@coconut.itojun.org> Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk < said: > Does anybody plan to use sys/netkey? I've modified it for my IPsec > stack so I have a modified version that compiles and works. > However, part of my modification may break backward compatibility. > So, I would like to know who is needing sys/netkey. I originally put in in the hope that it could be used as a generic key-management mechanism for more than just ipsec. (In particular, routing protocols.) Since it's really quite moldy now, and never ended up being used for that purpose, I don't have any particular attachment for what's there. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message