From owner-freebsd-current Sat Feb 19 19:46:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0391237BD9A; Sat, 19 Feb 2000 19:46:51 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id TAA02519; Sat, 19 Feb 2000 19:46:50 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 19:46:50 -0800 (PST) From: Kris Kennaway To: Doug Barton Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-Reply-To: <38AF5F59.A0BEC49@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Doug Barton wrote: > Pardon me for coming late to the party, but what was the > rationale behind putting openssl into the source anyway? Given the > rsa/no rsa problems, not to mention the US vs. the world problems, > what were the benefits that outweighed the complications? Note, I'm > not trying to be critical here, I'm just interested in the thought > process behind the decision. Having _a_ general-purpose cryptography toolkit in the base system allows us to add in all sorts of cool things to FreeBSD (https support for fetch, openssh, random cryptographic enhancements elsewhere). OpenSSL just happens to be the only decent freely-available (BSDL) toolkit. The patent nonsense with RSA will be going away in september, and the US vs. the world problems have also been receding and probably won't last much longer either. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message