28 May
2013
28 May
'13
7:10 p.m.
On 5/28/13 11:06 AM, Klaus Darilion wrote:
On 28.05.2013 10:20, Olle E. Johansson wrote:
This is not an issue anymore, now tls
module is the one initializing
first. Everything works fine for the latest several stable releases.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
* http://asipto.com/u/katu *
28 maj 2013 kl. 10:15 skrev Peter
Dunkley<peter.dunkley(a)crocodile-rcs.com>om>:
I was worried about the initialization of
OpenSSL libraries. The
problem we had in Asterisk was that Asterisk initialized
several times and external libraries could do that as well - like
jabber and database libraries. I think Kevin solved that
by creating a small shim that made sure that only one call could be
made. I can see that it can happen here as
well with postgresql client libraries initializing OpenSSL by itself.
I remember that we had the postgresql openssl initialization problem
already in Kamailio (or was it ser?) and it was solved by having the
other module linking to openssl statically. No. This
information is incomplete and I have only provided this
information as there was a
discussion about OpenSSL during the
recent developer meeting - this mailing list is the correct place to
continue and conclude this discussion.