From owner-cvs-all Sat Jan 15 19:38:38 2000 Delivered-To: cvs-all@freebsd.org Received: from 1Cust212.tnt2.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7BF5B1516B; Sat, 15 Jan 2000 19:38:33 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Sat, 15 Jan 2000 22:38:31 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Kris Kennaway Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/secure/lib Makefile src/secure/usr.bin Makefile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk On Sat, 15 Jan 2000, Kris Kennaway wrote: > On Sat, 15 Jan 2000, Brian Feldman wrote: > > > Log: > > We cannot have libcrypto, and therefore OpenSSL at all, without RSA. > > If you need examples of breakage, I'm ready to provide more than a > > few. > > Brian, there was no call to unilaterally back this out without discussing > it with me first. There are certainly many reasons to have libcrypto > without RSA, and indeed anyone who wants to use libcrypto in a commercial > setting will have to make do that way (and obviously any ports which > require RSA cannot be used by them). As you well know, RSAref support is > coming; in the meantime, libcrypto and libssl work perfectly well for > OpenSSL ports which don't require RSA (w3m-ssl is one I've tested). In the meantime, it also breaks (e.g.) OpenSSH. This is _not_ acceptable. Yes, there was a call: it had to be out ASAP before it broke more people than it probably already has. I hope that's not too many. Think like a user: do you want broken apps? > Kris -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message