[asterisk-dev] [Code Review] Wrap OpenSSL library initialization to make it safe for loaded modules to also use OpenSSL.

[reviewboard at asterisk.org]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/1006/#review2919
-----------------------------------------------------------


This isn't really a message to Kevin, but more to everyone else:

For those that have seen this problem before, can someone please open a report on issues.asterisk.org that discusses a situation where you have hit the problem?  Also, could you please test this to verify that it solves the problems you have seen?

- Russell


On 2010-11-11 16:14:40, Kevin Fleming wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/1006/
> -----------------------------------------------------------
> 
> (Updated 2010-11-11 16:14:40)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Summary
> -------
> 
> During the devcon after AstriCon 2010, we got a report that using PostgreSQL from within Asterisk, when the PostgreSQL connections are configured to use SSL/TLS to connect to the database server, can cause random crashes and other bizarre behavior. The reporter said this was known to be an issue with some other packages as well (notably Kamailio), and had to do with both Asterisk and the PostgreSQL libraries assuming they "owned" the OpenSSL libraries in the process' memory space, and thus calling initialization code twice (or worse).
> 
> This patch addresses this problem by using dynamic linker functionality to *wrap* the real OpenSSL initialization functions (and some other dangerous ones) with versions that don't actually do anything, and then calling the real ones only *one* time during Asterisk startup. To make this work, the SSL functionality that is normally built into the main Asterisk binary now must be built into a dynamic library (libasteriskssl.so), which is installed into the standard dynamic library location on the system (this is *not* an Asterisk loadable module, just a regular dynamic library).
> 
> As part of this patch, the usage of ASTLIBDIR throughout the build system to refer to the directory where Asterisk loadable modules are installed was changed to ASTMODDIR (which matches how it is referred to in the source code and in asterisk.conf), and a new definition of ASTLIBDIR was created to point to the system's dynamic library directory.
> 
> 
> Diffs
> -----
> 
>   /trunk/Makefile 294735 
>   /trunk/Makefile.moddir_rules 294735 
>   /trunk/build_tools/make_defaults_h 294735 
>   /trunk/build_tools/mkpkgconfig 294735 
>   /trunk/configure UNKNOWN 
>   /trunk/configure.ac 294735 
>   /trunk/main/Makefile 294735 
>   /trunk/main/ssl.c 294683 
>   /trunk/main/ssl.c 294735 
>   /trunk/makeopts.in 294735 
> 
> Diff: https://reviewboard.asterisk.org/r/1006/diff
> 
> 
> Testing
> -------
> 
> Compiles and runs on Linux x86-64 with no apparent change in behavior. The Makefile bits to install libasteriskssl.so in the right place will probably have to be checked by Solaris, Darwin and *BSD users to get them right.
> 
> 
> Thanks,
> 
> Kevin
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20101116/b6ef0239/attachment.htm