[asterisk-bugs] [JIRA] (ASTERISK-26126) [patch] leverage 'bindaddr' for TLS in http.conf

[Richard Mudgett (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Mudgett updated ASTERISK-26126:
---------------------------------------

    Status: Open  (was: Triage)

> [patch] leverage 'bindaddr' for TLS in http.conf
> ------------------------------------------------
>
>                 Key: ASTERISK-26126
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26126
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/HTTP
>    Affects Versions: 11.22.0, 13.9.1
>            Reporter: Alexander Traud
>            Severity: Minor
>         Attachments: secure_websocket.patch
>
>
> The internal HTTP/WebSocket server supports both TCP and TLS, which can be activated separately via the file {{http.conf}}. The source code intends to re-use the TCP parameter {{bindaddr}} for TLS, even if {{tlsbindaddr}} is not specified explicitly. This did not work because of a typo. The attached resolves this typo.
> Although looking cosmetic on the first glance, this bug was reported, because {{http.conf.sample}} states {{tlsbindaddr}} would default to {{bindaddr}} – and I lost an hour because of that. This is a regression of [Review Board 986|https://reviewboard.asterisk.org/r/986/] by [~mmichelson].



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