Date: Thu, 9 Dec 1999 18:24:47 -0800 (PST) From: Kris Kennaway <kris@hub.freebsd.org> To: Archie Cobbs <archie@whistle.com> Cc: cvs-committers@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Crypto in the kernel: where & how? Message-ID: <Pine.BSF.4.21.9912091815460.68649-100000@hub.freebsd.org> In-Reply-To: <199912100101.RAA76788@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.9912091815460.68649-100000>