From owner-freebsd-hackers  Fri Dec 10  1: 8:52 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2FC6914A14; Fri, 10 Dec 1999 01:08:39 -0800 (PST)
	(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id LAA17808;
	Fri, 10 Dec 1999 11:06:46 +0200 (SAT)
	(envelope-from jhay)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199912100906.LAA17808@zibbi.mikom.csir.co.za>
Subject: Re: Crypto in the kernel: where & how?
In-Reply-To: <199912100741.dBA7fgW23996@gratis.grondar.za> from Mark Murray at "Dec 10, 1999 09:41:41 am"
To: mark@grondar.za (Mark Murray)
Date: Fri, 10 Dec 1999 11:06:46 +0200 (SAT)
Cc: archie@whistle.com (Archie Cobbs), cvs-committers@FreeBSD.org,
	freebsd-hackers@FreeBSD.org
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > What is the plan (if any) for including crypto stuff in the kernel?
> > As time goes on this will be more and more needed, eg. for IPSec
> > and other VPN applications.
> 
> The KAME/IPv6 guys have already brought this up; the agreement was
> that...
> 
> > It would be nice if we had a /usr/src/sys/crypt directory, plus whatever
> > export-controlled firewalling silliness is necessary.
> 
> ...a sys/crypt/ directory should hold their DES code. :-)
           ^^^^^
Shouldn't this be crypto ? That is what I see if I look on internat
in the /usr/local/etc/cvsup/sup directory.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za


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