From owner-freebsd-security Thu Jul 27 9:11:23 2000 Delivered-To: freebsd-security@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id B5F9E37B52F for ; Thu, 27 Jul 2000 09:11:18 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id MAA95905; Thu, 27 Jul 2000 12:11:16 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 27 Jul 2000 12:11:16 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-security@FreeBSD.org Cc: ogud@tislabs.com Subject: MFC'ing OpenSSL 0.9.5a? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A co-worker of mine pointed out that FreeBSD 4.1-RELEASE shipped with OpenSSL 0.9.4, which apparently causes problems for BIND9 due to API changes between versions, and bugs in 0.9.4. FreeBSD 5.0-CURRENT appears to be using OpenSSL 0.9.5a; I was wondering if there were any plans to MFC the new version of OpenSSL? Of course, people only bring these things up after releases, but it would be nice to have it in the immediate -STABLE upgrade path, and in time for the November post-RSA-patent release. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message