Re: [apache-ssl] Patch to apache_1.3.0+ssl_1.22
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [apache-ssl] Patch to apache_1.3.0+ssl_1.22




In article <35EADB7C.49D6C169@algroup.co.uk> you wrote:
> Randall S. Winchester wrote:
>> 
>> We were seeing segmentation faults, and this worked around a frequent case
>> of ssl == NULL. We noticed this when additional auth_ code we we using was
>> not being reached. It was otherwise not obvious.

> But how can this be? SSLClose() is not registered as a cleanup until
> after conn->client->ssl has been set. Unless I'm missing somewhere where
> it gets set to NULL later on.

Yes, although mod_ssl 2.0.6 already has a similar if-statement in his socket
close hook, I've asked myself this question last time, too. From the code I
couldn't find any code which would lead to a conn->client->ssl to be NULL for
the close hook. The only reason I can image here is some internal crossing of
cleanup and setup procedures in the Apache kernel. Hmmmm... any clues?

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com