From owner-freebsd-current  Sat Feb 19 20: 7: 2 2000
Delivered-To: freebsd-current@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP
	id 89A7137BDF9; Sat, 19 Feb 2000 20:06:59 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA42147;
	Sat, 19 Feb 2000 20:06:52 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Kris Kennaway <kris@FreeBSD.org>
Cc: Victor Salaman <salaman@teknos.com>, freebsd-current@FreeBSD.org
Subject: Re: openssl in -current 
In-reply-to: Your message of "Sat, 19 Feb 2000 18:31:09 PST."
             <Pine.BSF.4.21.0002191820430.98202-100000@freefall.freebsd.org> 
Date: Sat, 19 Feb 2000 20:06:52 -0800
Message-ID: <42144.951019612@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hmmm.  I'm beginning to wonder if openssl shouldn't just be backed-out
at this point.  The situation with RSA makes this far more problematic
than I think anyone first thought, and I've seen a lot of breakage so
far for what appears to be comparatively little gain over what we had
before with the ports collection version.

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message