[asterisk-bugs] [JIRA] (ASTERISK-26744) Asterisk fails to start up when using OpenSSL 1.1.0

Bernhard (JIRA) noreply at issues.asterisk.org
Mon Jan 30 18:23:09 CST 2017


    [ https://issues.asterisk.org/jira/browse/ASTERISK-26744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234945#comment-234945 ] 

Bernhard commented on ASTERISK-26744:
-------------------------------------

Understood. But please accept that I am not motivated to go through the license agreement hassle. Maybe someone with gerrit access can link to this issue. The information about the problem at hand is documented here for everyone to look up, which was my primary goal.

> Asterisk fails to start up when using OpenSSL 1.1.0
> ---------------------------------------------------
>
>                 Key: ASTERISK-26744
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26744
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General
>    Affects Versions: 14.2.1, GIT
>         Environment: Debian testing (stretch) using libssl-dev 1.1.0c-2
>            Reporter: Bernhard
>
> After manually applying https://gerrit.asterisk.org/#/c/4753/1 (currently pending review), compilation of asterisk succeeds (gerrit git master). Compilation fails for 14.2.1, also see ASTERISK-26109
> However, asterisk fails to start up issuing message: "SSL initialization failed" on the console.
> It turns out that {{ast_ssl_init}} returns -1 since {{SSL_library_init}} is now a macro, so {{get_OpenSSL_function}} using the dynamic linker fails to lookup the real {{SSL_library_init}} function.
> As far as my research went, all the initialization done in {{ast_ssl_init}} is obsolete as of OpenSSL 1.1.0, so IMHO the compiler directive testing for {{HAVE_OPENSSL}} should be extended to hide the code for OpenSSL >= 1.1.0.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list