https://bz.apache.org/bugzilla/show_bug.cgi?id=60947
--- Comment #3 from Jacob Champion <[email protected]> --- (In reply to Paul Spangler from comment #2) > This comment isn't related to the particular issue you've described with the > callback, but is related to the title of the bug. We've also seen a rare > segfault when mixing mod_ssl with APR-crypto, but in SSL_load_error_strings > (which is supposedly fixed in 1.1.0, see > https://rt.openssl.org/Ticket/Display.html?user=guest&pass=guest&id=2325): Nice, thanks for the link! More evidence that perhaps the long-term fix for these sorts of problems is just to move to 1.1.0, where they've done away with a lot of the static global initialization stuff... > Maybe the "fix" here would also be to pin whatever the callback points to in > memory (if that would even be feasible) so it survives a mod_ssl reload? Interesting idea. I suppose we could have the callback(s) live in a completely separate DSO that never gets unloaded. Feels like the bang-for-buck might not be there, if this is a problem that's just going to go away after everyone finally updates to 1.1.0-or-later. *If* we have to keep supporting stuff like 0.9.8 forever, though, it might be worth a shot. Keep an eye on my recent dev thread [1]; maybe someone will have some input on that front. [1] https://lists.apache.org/thread.html/15c735e7c513f150a534bc0be69c101106b4d64d076f2c22e2a0ad52@%3Cdev.httpd.apache.org%3E -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
