From owner-freebsd-hackers  Thu Dec  9 17: 1:46 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3B8A11572D; Thu,  9 Dec 1999 17:01:39 -0800 (PST)
	(envelope-from archie@whistle.com)
Received: (from archie@localhost)
	by bubba.whistle.com (8.9.2/8.9.2) id RAA76788;
	Thu, 9 Dec 1999 17:01:39 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199912100101.RAA76788@bubba.whistle.com>
Subject: Crypto in the kernel: where & how?
To: cvs-committers@freebsd.org, freebsd-hackers@freebsd.org
Date: Thu, 9 Dec 1999 17:01:38 -0800 (PST)
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.

It would be nice if we had a /usr/src/sys/crypt directory, plus whatever
export-controlled firewalling silliness is necessary.

Proposal.. (to get things started)

  - Add /usr/src/sys/crypt directory
  - Put exportable crypto stuff in it, eg, md5.c.
  - Put non-exportable crypto stuff in the international repository
    (which is where?) .. and possibly a separate US repository (?)
    (Or can the CVSup mirrors be configured not to mirror it?)

My ulterior motive is to checkin netgrapph/ng_mppc.c which adds
MPPE/MPPC support for PPTP.  However it's useless without an [A]RC4
implementation.

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com


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