Author: Tim Wilde Date: To: Chris Lightfoot CC: exim-users Subject: Re: [exim] Segmentation Fault on STARTTLS
Chris Lightfoot wrote: > indeed... the only thing that strikes me there is the
> value of dhparam gdb is reporting in the params of
> tls_init (it should be an expansion string used to
> identify a DH parameters file); either the passed value
> was invalid (which seems surprising since by that point
> it's been successfully used by init_dh()) or the stack is
> being corrupted somewhere along the way.
With a little experimentation, I've figured it out. In the course of
proving I wasn't crazy about getting this working on a different system,
I copied my Local/Makefile and configuration to a FreeBSD 4.11 system.
That system, however, doesn't have MySQL installed, so I had to disable
that in my configuration. On that system, TLS worked fine. For
completeness of testing, I then disabled LOOKUP_MYSQL and the associated
libs on my FreeBSD 6.1 system, rebuilt, installed, tested, and, lo and
behold, TLS worked just fine! So it seems that there's some sort of
conflict between the MySQL client and OpenSSL (which is odd, since the
MySQL client is actually linked against OpenSSL itself, a fact which I
discovered when trying to link Exim against a different OpenSSL
version). In case anyone wants to try to track it down, the MySQL
client I was linking against was the official MySQL binary
mysql-standard-5.0.26-freebsd6.0-i386.
I don't actually need LOOKUP_MYSQL right now, so I've gone ahead and
disabled it, though I can happily play with it some more if there's a
desire to do any further debugging of the problem at the Exim level.
