On Wed, Mar 03, 1999, [EMAIL PROTECTED] wrote:
> > Ok, I've now found and successfully fixed this problem for mod_ssl 2.2.4.
>
> Is this the same re-start bug that's been around for a while?
> At what point was this bug introduced? As of the very first EAPI based
> mod_ssl?
No, it's a totally different bug I introduced in 2.2.3 while fixing another
one (the DSO core dumps). It's not present in 2.2.2 or below AFAIK.
> Would it be possible to get a synopsis of what needs to be done to get rid
> of this bug? I have mod_ssl 2.1.3 that I have all hacked up, and would
> prefer to simply patch it, as opposed to upgrade to the latest, and re-hack
> it all up. It would be a real pain, for me, to have to always upgrade to
> the latest mod_ssl to get a bug fix especially when I do not need any new
> features.
You've no problem in 2.1.3 because as I said, the bug was introduced with code
comitted for 2.2.3. But in general when you want to fix a locally patched up
version you should grab the CVS repository and look at the fixes in details
with ``cvs diff -rMOD_SSL_2_X_Y <file>''. All mod_ssl versions have tags, so
when the next days after 2.2.4 went out you can see the fixed in detail by
using ``cvs diff -rMOD_SSL_2_2_3 -rMOD_SSL_2_2_4''. Alternatively you can also
extract the two corresponding tarballs and perform the diff, of course.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
