Date: Wed, 11 Sep 2002 16:31:51 +0200 From: Ruben de Groot <fbsd-q@bzerk.org> To: "Jack L. Stone" <jackstone@sage-one.net> Cc: Daniel Larsson <daniell@servicefactory.se>, freebsd-questions@FreeBSD.ORG Subject: Re: Status of port apache13-ssl Message-ID: <20020911143151.GA58407@ei.bzerk.org> In-Reply-To: <3.0.5.32.20020911082528.00fbeac8@mail.sage-one.net> References: <1031749460.13469.8.camel@daniell.servicefactory.se> <3.0.5.32.20020911082528.00fbeac8@mail.sage-one.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 11, 2002 at 08:25:28AM -0500, Jack L. Stone typed: > At 03:04 PM 9.11.2002 +0200, Daniel Larsson wrote: > >Currently the apache13-ssl port is marked "FORBIDDEN", due to the > >security holes found in Apache before and including 1.3.24. However, > >there is a more recent version of Apache-SSL, named > >apache_1.3.26+ssl_1.48. Does anyone know the reasons why this port > >hasn't been updated yet? Is apache-modssl in much more wide spread use > >than apache-ssl, so noone is bothered? Or are there some other problems > >currently with apache-ssl I am not aware of? Any insights appreciated :) > >-- > >Daniel Larsson > > > > Are your ports up to date? Mine shows this: > Port: apache+mod_ssl-1.3.26+2.8.10 > Path: /usr/ports/www/apache13-modssl You didn't read his question. He's asking about apache-ssl, not apache-mod_ssl > Info: The Apache 1.3 webserver with SSL/TLS functionality > Maint: ports@FreeBSD.org > > Best regards, > Jack L. Stone, > Administrator > > SageOne Net > http://www.sage-one.net > jackstone@sage-one.net > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020911143151.GA58407>