From owner-freebsd-hackers Wed Sep 6 13:46:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4401E37B424; Wed, 6 Sep 2000 13:46:14 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA59534; Wed, 6 Sep 2000 13:46:14 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 6 Sep 2000 13:46:14 -0700 (PDT) From: Kris Kennaway To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: FYI: RSA Donated to the public domain In-Reply-To: <200009061317.HAA68280@harmony.village.org> 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 Wed, 6 Sep 2000, Warner Losh wrote: > In message <200009061312.HAA68224@harmony.village.org> Warner Losh writes: > : RSA Security Releases RSA Encryption Algorithm into Public Domain > > Note that other information at the site says that RSAREF isn't > released into the public domain. Its use is still governed by > copyright law, so we'll have to use the international version of > RSAREF if we want to get RSA into -current. There's no reason why we would want to continue to use RSAREF, except perhaps for source code compatability with something that was written to link against it. The OpenSSL implementation is much better, and basically we just have to build it by default now. I'm not sure whether it's okay to build a shim for OpenSSL which translates the RSAREF API into the native one (the reverse of the OpenSSL -> RSAREF code which currently exists), but it would be mildly useful for those legacy apps. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message