From owner-freebsd-hackers Thu Dec 9 18:24:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id B352315715; Thu, 9 Dec 1999 18:24:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A29311CD750; Thu, 9 Dec 1999 18:24:47 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 9 Dec 1999 18:24:47 -0800 (PST) From: Kris Kennaway To: Archie Cobbs Cc: cvs-committers@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Crypto in the kernel: where & how? In-Reply-To: <199912100101.RAA76788@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Dec 1999, Archie Cobbs wrote: > It would be nice if we had a /usr/src/sys/crypt directory, plus whatever > export-controlled firewalling silliness is necessary. It'd presumably have to be /usr/src/secure/sys to fit with our existing distribution infrastructure. > - Add /usr/src/sys/crypt directory ^o > - Put exportable crypto stuff in it, eg, md5.c. > - Put non-exportable crypto stuff in the international repository > (which is where?) internat.freebsd.org, in south africa > .. and possibly a separate US repository (?) > (Or can the CVSup mirrors be configured not to mirror it?) US sites mirror their crypto from freebsd.org, international ones from the international repository. The preferred path is for code to be committed by international people to the international repository, since it can be imported from there back into the US - if we can avoid it we shouldn't commit stuff to the US repository on its own since that prevents most of our users (by geography) from accessing it. However at least in the case of OpenSSL (which I'm planning to import into internat when I go home to australia next week :-) the two will have to be divergent due to the patent restrictions on RSA. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message