From owner-freebsd-ports Wed Jul 30 12:37:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA27876 for ports-outgoing; Wed, 30 Jul 1997 12:37:01 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA27857 for ; Wed, 30 Jul 1997 12:36:55 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id NAA26520; Wed, 30 Jul 1997 13:36:37 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id NAA21129; Wed, 30 Jul 1997 13:38:02 -0600 (MDT) Date: Wed, 30 Jul 1997 13:38:02 -0600 (MDT) From: Marc Slemko To: Adam David cc: freebsd-ports@FreeBSD.ORG Subject: Re: apache_1.2.0+ssl_1.8.tar.gz is out In-Reply-To: <199707301828.SAA08049@ubiq.veda.is> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 30 Jul 1997, Adam David wrote: > >I found out, that there are new apache SSLeay patches out. > > >FTP Directory: ftp://ftp.ox.ac.uk/pub/crypto/SSL/ > > > README . . . . . . . . . . . . . [May 29 15:58] 6k > > README.066 . . . . . . . . . . . [May 29 15:59] 2k > > README.080 . . . . . . . . . . . [Jul 1 12:44] 5k > > SSLeay-0.6.6.patch1. . . . . . . [May 29 17:15] 1k > > SSLeay-0.6.6.tar.gz. . . . . . . [May 29 17:15] 814k > > SSLeay-0.8.0.README. . . . . . . [Jul 1 12:44] 1k > > SSLeay-0.8.0.tar.gz. . . . . . . [Jul 3 15:12] 968k > > apache_1.1.1+1.3.ssl.tar.gz. . . [Jul 16 1996] 21k > > apache_1.2.0+ssl_1.8.tar.gz. . . [Jul 7 09:56] 24k > > apache_1.2b10+ssl_1.6.tar.gz . . [May 3 21:41] 22k > > >Do you plan to upgrade the apache port with that changes > >so that a secure server would be made possible ? > > And does this mean SSLeay-0.8 is needed as a separate port from -0.6.6 ? > (i.e. does anything worthwhile depend on the previous version, either within > the ports tree or outside of it?) You can use 1.2.0+ssl_1.8 with SSLeay-0.6.6 if you really want, but it is probably better to go for 0.8.1. There may well be problems upgrading it; short term it may be better to add a seperate port for 0.8.1. Note that 1.2.0+ssl_1.8 doesn't apply cleanly against 1.2.1 (or 1.2.2 when it comes out), but it is pretty easy to patch in the other parts by hand.