[asterisk-bugs] [JIRA] (ASTERISK-28797) [patch] tcptls: Fix notice when TLS is enabled but not configured.

[Friendly Automation (JIRA)]

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

Friendly Automation commented on ASTERISK-28797:
------------------------------------------------

Change 14037 merged by Friendly Automation:
tcptls: Fix notice when TLS is enabled but not supported.

[https://gerrit.asterisk.org/c/asterisk/+/14037|https://gerrit.asterisk.org/c/asterisk/+/14037]

> [patch] tcptls: Fix notice when TLS is enabled but not configured.
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-28797
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28797
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General
>    Affects Versions: 13.32.0, 16.9.0, 17.3.0
>            Reporter: Alexander Traud
>            Assignee: Alexander Traud
>            Severity: Trivial
>              Labels: patch
>         Attachments: no_ssl_error.patch
>
>
> ASTERISK-27394 introduced a log message when Asterisk was configured (and build) without the OpenSSL Development Headers. That message is printed when a TLS _server_ is attempted by the administrator, for example through {{tlsenable=yes}} in the configuration file {{sip.conf}}.
> However
> 1. the log message did not end with a carriage return, resulting the next log message to be printed in the same line, and
> 2. another log message existed when the administrator attempted a TLS _client_.
> The attached patch adds the missing carriage return. Furthermore it uses the same wording and severity (not notice but error) for both log messages. This not only improves consistency, when both cases happen (TLS server and client requested by administrator) but also allows the administrator to distinguish which message belongs to the server and which to the client case.



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