[asterisk-bugs] [JIRA] (ASTERISK-24517) TLS support for Solaris, Ming and non-glibc Linux systems

Timo Teräs (JIRA) noreply at issues.asterisk.org
Mon Apr 20 06:29:33 CDT 2015


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

Timo Teräs commented on ASTERISK-24517:
---------------------------------------

seems it is not possible easily after all. E.g. app_externalivr shares the same code path for forked process along with tls/tcp code.

So my suggestions is to make a new abstraction for iostreams. See attached patch. It's intended as draft of what I'm working, and is not fully tested or commented. But at least it compiles, and AMI-over-http login worked.

> TLS support for Solaris, Ming and non-glibc Linux systems
> ---------------------------------------------------------
>
>                 Key: ASTERISK-24517
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24517
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Core/Portability
>    Affects Versions: 12.7.0, 13.0.0
>            Reporter: Timo Teräs
>            Assignee: Timo Teräs
>         Attachments: 0001-convert-to-ast_iostream.patch
>
>
> TLS is not working on systems without funopen(3) or fopencookie(3). This is a major portability issue as both functions are non-standard extensions.
> Per comment in ASTERISK-15490 I'm creating this improvement issue, as I don't see this bug being created earlier. ASTERISK-24515 is also related, but it is about *regression* of now defunct regular (non-TLS) connections. This bug is about adding the TLS-support for platforms that have never worked earlier.



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



More information about the asterisk-bugs mailing list