Re: ??? 1.3.23
In article [EMAIL PROTECTED] you wrote: When is planned the final release ? For today. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
RE: ??? 1.3.23
When is planned the final release ? Thanks for letting us know. Gilles -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ralf S. Engelschall Sent: Monday, January 28, 2002 12:22 PM To: [EMAIL PROTECTED] Subject: Re: ??? 1.3.23 On Mon, Jan 28, 2002, Ralf S. Engelschall wrote: [...] And, the mod_ssl I get from CVS is for 1.3.20, which is *less* than the one that is downloadable already built for 1.3.22, shooting holes in my initial theory that going to the CVS was even getting me closer to now... Ops, my fault. The rsync cronjob was broken which updated the CVS copy from my master machine. Now fixed. For Apache 1.3.23: Expect an mod_ssl update for 1.3.23 within the next days. The mod_ssl CVS not got Apache 1.3.23 imporated and the patch set was updated. I'm still incorporating other bugfixes before 2.8.6 will be released the next days. In the meantime you already can find the latest CVS state as mod_ssl-SNAP-20020128.tar.gz (or any newer) on the FTP server. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED] __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: ??? 1.3.23
On Mon, Jan 28, 2002, Ralf S. Engelschall wrote: [...] And, the mod_ssl I get from CVS is for 1.3.20, which is *less* than the one that is downloadable already built for 1.3.22, shooting holes in my initial theory that going to the CVS was even getting me closer to now... Ops, my fault. The rsync cronjob was broken which updated the CVS copy from my master machine. Now fixed. For Apache 1.3.23: Expect an mod_ssl update for 1.3.23 within the next days. The mod_ssl CVS not got Apache 1.3.23 imporated and the patch set was updated. I'm still incorporating other bugfixes before 2.8.6 will be released the next days. In the meantime you already can find the latest CVS state as mod_ssl-SNAP-20020128.tar.gz (or any newer) on the FTP server. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: ??? 1.3.23
P.S. I found the documentation on how to upgrade *modssl* later, using apxs. But that method doesn't seem to apply to upgrading *apache*... -Tom __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: ??? 1.3.23
On Sun, Jan 27, 2002, Tom Oehser wrote: [...] And, the mod_ssl I get from CVS is for 1.3.20, which is *less* than the one that is downloadable already built for 1.3.22, shooting holes in my initial theory that going to the CVS was even getting me closer to now... Ops, my fault. The rsync cronjob was broken which updated the CVS copy from my master machine. Now fixed. For Apache 1.3.23: Expect an mod_ssl update for 1.3.23 within the next days. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: ??? 1.3.23
On Sun, 27 Jan 2002, Tom Oehser wrote: I found the documentation on how to upgrade *modssl* later, using apxs. But that method doesn't seem to apply to upgrading *apache*... The short answer is that while it *can* be done, it's a very manual process and it's highly prone to mistakes. If you insist on doing it by hand, there's a flag you can give to mod_ssl's configure to force it to try to apply itself to a version it wasn't designed to work with (--force), but don't be surprised if you get patching errors and have to manually tweak the Apache source afterward to get it to (a) compile and (b) run correctly. The safest bet by far is to just wait on the new version of mod_ssl to be released. --Cliff -- Cliff Woolley [EMAIL PROTECTED] __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]