From owner-freebsd-security Thu Jul 27 23: 6:48 2000 Delivered-To: freebsd-security@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8DA0E37B72F; Thu, 27 Jul 2000 23:06:45 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA18804; Thu, 27 Jul 2000 23:06:45 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 27 Jul 2000 23:06:45 -0700 (PDT) From: Kris Kennaway To: Robert Watson Cc: freebsd-security@FreeBSD.org, ogud@tislabs.com Subject: Re: MFC'ing OpenSSL 0.9.5a? In-Reply-To: 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 On Thu, 27 Jul 2000, Robert Watson wrote: > 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. Several people had weird problems with 0.9.5a which I could never reproduce or track down - this made me nervous to merge it. If I had some success stories of people who have successfully run SSL webservers using it in -current it might ease my fears somewhat :-) 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-security" in the body of the message