From owner-freebsd-hackers Fri Dec 10 12:15:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 6031715F56; Fri, 10 Dec 1999 11:57:14 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D0841CD79B; Fri, 10 Dec 1999 11:57:14 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 10 Dec 1999 11:57:14 -0800 (PST) From: Kris Kennaway To: Dan Moschuk Cc: Archie Cobbs , cvs-committers@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Crypto in the kernel: where & how? In-Reply-To: <19991210145201.G3187@spirit.jaded.net> 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 Fri, 10 Dec 1999, Dan Moschuk wrote: > | 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. > > The RSA patent makes things a lot more difficult. If we do add some crypto > into the kernel I suggest we use patent-free algorithms to start with. This was actually part of an unrelated point I was making - RSA will definitely not be going into the kernel anywhere at this point! In general, we want the two crypto repositories to stay in sync which generally means propagating from internat -> freefall, but we can't do it for RSA. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message