I wouldn't expect an update until it's in sync with the final 0.9.8m from
the group, as a (probably final) update. Without 0.9.8m finished, due to
an unfinished RFC, it's a bit trickier to move ahead.
On 2/5/2010 6:19 AM, Bernard PREVOSTO wrote:
The Apache Group is pleased to announce the
Brian Sieler wrote:
Using apache 2.2.x.
Because mod_ssl in Apache 2.0 2.2 is maintained by the httpd project
(with some good collaboration that moves fixes from that ASF flavor to
the mod_ssl project and back, when applicable)...
you might have meant to ask this question of [EMAIL PROTECTED]
http://hunter.campbus.com/ - and yes Chris is trustworthy. Blame Canada :)
Bill
Eckard Wille wrote:
Erol Yalaz schrieb:
I have a WIN2003 box with the latest Apache on it (2.2.3) and it is
working great. I need to get mod_ssl working. Unfortunately, I can’t
Any suggestions? Shouldn’t
FYI - if you are asking, there's no announce yet since 1.3.36 simply fixes
the Include directive regressions introduced in 1.3.35, if you either nested
your Include directive in a Something /Something block, or you used the
wildcard match for your Include directive. It will be some time before
Joe Orton wrote:
On Mon, May 08, 2006 at 08:58:42AM +0200, Ralf S. Engelschall wrote:
On Tue, Apr 04, 2006, Love Hörnquist Åstrand wrote:
(gdb) bt
#0 CRYPTO_get_ex_data (ad=0xe8, idx=137019688) at ex_data.c:628
#1 0x4035c035 in SSL_get_ex_data (s=0x1, idx=296) at ssl_lib.c:2220
Looks
Ralf S. Engelschall wrote:
On Fri, May 05, 2006, William A. Rowe, Jr. wrote:
Ping, in anticipation of a 2.8.26 for 1.3.35 (are we expecting one?)
I didn't see any feedback, do any of the Apache guru's have comments? Any
clarifications? (I hope I made the specifics clear enough, below
Ping, in anticipation of a 2.8.26 for 1.3.35 (are we expecting one?)
I didn't see any feedback, do any of the Apache guru's have comments? Any
clarifications? (I hope I made the specifics clear enough, below.)
Yours,
Bill
William A. Rowe, Jr. wrote:
Maintainers,
This patch addresses
Eckard Wille wrote:
Kevin Smith schrieb:
Probably the best think to do is add the absolute path to the files as:
SSLCertificateFile C:/Program Files/Apache2/conf/ssl/servername.cert
SSLCertificateKeyFile C:/Program Files/Apache2/conf/ssl/servername.key
If this still does not work try to
The following patches mop up some unnecessary compile warnings, when the
functions are properly decorated. It's been sitting in my drafts waiting
for a subscription to go through for 3 months, so feel free to verify that
they are still appropriate.
--- mod_ssl.h 25 Oct 2005 04:32:42 -
Maintainers,
This patch addresses a still-outstanding flaw in mod_ssl, on *all* platforms.
However it's rarely evident on any platform other than Win32, because only Win32
recycles memory -so quickly- on other threads, that the cleanup cannot be
invoked.
Instead, in the LogRequest
Ralf and company,
I've been working with the EAPI patch for CovalentSSL, and discovered
two issues that will greatly improve EAPI compatibility for everyone!
One aspect, the exported symbols, can be remedied once and for all,
assuring some level of compatibility from version 1.3.15 forward
11 matches
Mail list logo
